I just discovered the AssetReference class, which seemed like a good way to allow me to assign references to Addressables in the inspector, like so:

The issue I’m having, though, is that when I have a handle on that Asset Reference, I don’t seem to correlate it to the “Asset Address” of the asset as set on the Addressables window:
Is there a simple thing I’m missing that allows me to extract the Asset Address from a AssetReference? I’m mainly using Asset Address in this one config, to make it easy to pick addressables, but in my code I’m almost always referring to addressables by their Address using constants.
Hey @dgoyette yeah there isn’t a direct way to get that information from something like an asset reference. I think it mainly has to do with the fact that we could have multiple ResourceLocations associated with a particular Addressable Asset, one of which is the Addressable Address you see in the GUI. We could look into adding something onto AssetReference that returned all of these locations…
I threw this together real quick as a potential for you to use modify it to make it work for your situation. Of course, if you end up finding multiple locations in the locator for your reference it might not be the first location like I have assumed in the quick example code below.
public AssetReference reference;
IEnumerator Start()
{
yield return Addressables.InitializeAsync();
foreach (var locator in Addressables.ResourceLocators)
{
IList<IResourceLocation> locations;
if (locator.Locate(reference.RuntimeKey, null, out locations))
{
Debug.Log(locations[0].InternalId);
}
}
}
Hope this helps
2 Likes
Thanks very much. I’ll take a look.
Thanks. It looks like this gives me what I want. The “InternalId” gives me the “Path” of the addressable, while “PrimaryKey” gives the short name or “Asset Address”. Hopefully this all still works in a build. 

Yes, It works at runtime.
Awesome, glad that helped