Bug Addressables causes build to fail

Before I begin, I want to say I've read through and tried the solutions for all the related threads and bug reports I've been able to find about this issue (like this one and this one), and yet haven't been able to find a solution, hence my posting another thread.

While I'm not able to upload my log file, it contains many lovely errors including but not limited to:

OperationException : Addressables - Unable to load runtime data at location UnityEngine.ResourceManagement.AsyncOperations.AsyncOperationHandle`1[[UnityEngine.AddressableAssets.Initialization.ResourceManagerRuntimeData, Unity.Addressables, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null]].

RuntimeData is null. Please ensure you have built the correct Player Content.

No Locale could be selected:
No Locales were available. Did you build the Addressables?

OperationException : SelectedLocale is null. Could not load table.​

Now, I've tried clearing and rebuilding my addressables, I've tried running the localization analyzers, I've confirmed the build and load paths of the addressables, etc, but no luck.
(I'm using Unity 2020.3.28, Addressables 1.19.19, and Localization 1.3.2)

I don't know if tagging is allowed here, but @karl_jones seems to be the man to call from the dozen other threads I've just read through in the past two hours.

 

I was building for Windows, but something strange has happened. In the middle of trying to check what you just wrote, my computer spontaneously crashed on me and shut down. When everything powered back on again and I launched Unity, my localization stuff is still working as it was, but all the build errors have gone away. I've gone and checked all the addressables settings and nothing seems to have notably changed, but it looks like a random Windows 11 system crash seems to have magically fixed the problem?

 

Now that you say that, I don't think I had restarted the editor since it came up, but in these last 5 minutes I've discovered a new issue. Everything is building error free now, but somehow the build is not using the most up to date localization tables. For example, if I go and switch a value in the localization table from "New Game" to "Blahdy Blah", in the editor the button now displays "Blahdy Blah", but when I Build and Run, it's still using "New Game"

 

To fix that, I've gone back and cleared and rebuilt the addressables, and now the localization tables are updating again...but we're right back to the exact same string of errors I had at the start of this thread. To answer your previous question, no the errors do not show up in the editor even if I change the addressable play mode to use existing build

 

Nope, no errors regardless in the editor

 

It was initially running from C:\Users\[User]\Downloads\Build, but I just ran it from C:\Build and no difference

 

First error to show up is:

OperationException : Addressables - Unable to load runtime data at location UnityEngine.ResourceManagement.AsyncOperations.AsyncOperationHandle`1[[UnityEngine.AddressableAssets.Initialization.ResourceManagerRuntimeData, Unity.Addressables, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null]].​

Where would I see the StreamingAssets directory? Currently the build generates the .exe file, a MonoBleedingEdge folder, a Data folder, the Unity crash handler and the two .dll files

 

The data folder only has 'Managed' and 'Resources' directories (plus loose files), neither of which contain any subdirectories.

 

No custom build chain--I'm not smart enough for that.

The Library folder does have a 'com.unity.addressables' folder, and inside it does have an 'aa' folder filled with files, which if I understand correctly is what's meant to be copied to the nonexistent StramingAssets folder in the build

 

Copy the AA so that it's Data/StreamingAssets/AA/Windows or copy the contents of AA/Windows

 

Doesn't matter I tried both and neither changed a thing

 

By saving the log as a .txt I can upload it and share it with you

 

No...I copied the aa folder exactly from the Library folder, so it's:
'C:/Users/depog/Downloads/Test/SpritesheetTest_Data/StreamingAssets/aa/Windows/settings.json'.

Moving things out of that Windows directory worked, but how come the StreamingAssets folder didn't get created automatically? Should I be good moving forward?

 

Aha so it doesn't solve the problem moving forward. Whilst this build might work now that I've manually configured the files, I went ahead and changed one string in the localization tables, built the project again, and back to the errors

 

Got it--but that's a temporary fix, not the intended workflow, right?

 

Update: Suddenly (I can't tell you exactly what I changed to make this happen since it was after a full day of development on the project), as long as I manually clean and rebuild the addressables each time, when I make a build the StreamingAssets folder actually gets automatically created as it should. If I don't manually rebuild the addressables, the problem remains where no folders are getting created and I have to manually copy them over from the Library folder.

I'm guessing that ideally I shouldn't have to be manually doing either, but this is certainly better than no solution