Feeling kind of crazy with what I’ve seen, but it feels as though the UI for profile configuration in later Addressables versions isn’t keeping the “current profile I’m editing” in line with the changes I make. It’s almost as if I choose a non-active profile and make changes to load/build paths, that they’re actually being applied to the active profile. This has resulted in some wild situations where inexplicably my load paths are build paths instead, which makes the player all sorts of upset when it doesn’t know what ServerData is at runtime.
Just checking to see if this is on the radar, as while the verified package is serving it’s purpose I’m seeing a lot of stuff in the later revisions of Addressables that would potentially simplify a lot of current effort. Had been seeing this strange effect with whatever 1.16 is latest on the Unity registry.
Cheers and Happy Thanksgiving, y’all 
I’ll ping the team for an update.
Hm, that’s not something we’re aware of. We did do a pretty major rework of the profiles window so it’s possible something broke in there. Can you file a bug for this?
Also, good to see you Chris. It’s been a long time. I hope you’re doing well.
Yes I experience something similar. When modifying paths in the profile, I find that I have to hit enter then select the profile (in the left pane) I already have selected to ‘deselect’ it. Then I can ‘safely’ select a different profile.
What I found was if I edit a profile path, then select a different profile, it actually changes the path on the newly selected profile instead of the last selected (where I was editing it).
The UI is really broken in that way. It is really frustrating to work with. So many times I thought I had entered in paths correctly, but after building and testing, I run into exceptions, and later after exhaustively looking for the issue, I discover that the profile UI is the culprit.
All I can say, is be very very careful when editing the profiles. triple check using version control to see what the final paths are.