When the address of an Addressable contains an umlaut, the bundle flies contain the corrent umlaut.
But when unity requests the assetbundle during runtime, the umlauts are replaced with “?”.
This will result in a bundle not found error, since the address does not match the request.
Happens with Addressables 2.7.1.
Befor that we were on 1.18.15, here this bug was not present (I think)
Use Help => Report a bug especially if you can confirm that it used to work in older Addressables.
But generally I would strongly recommend, even to this day, to avoid non-ASCII characters in naming things. It’s still a very common source of issues.
And forever into the future… A to Z only, 0 to 9 if you feel lucky, and if you recently won the lottery, perhaps an underscore.
NEVER use spaces, NEVER use non-ASCII characters, NEVER use dashes or dots.
Remember, ALL software goes through testing. But when tested, they are simply NOT going to test all the whacky UTF-8 characters that someone might use.
If you decide you must have an umlaut or other whacky character, guess what?
You just became an UNPAID TEST PILOT!
This is not as easy as you think, when you don’t work alone but with Designers, Artists and asset from outside sources.
And what about Chinese, Japanese and other Countries which have no ASCII characters in their language?
None of that changes what I posted above.
Unity consists of dozens or even hundreds of different parts written by different people, different companies, all over the world through time. Every single part is tested by different people (humans!) with and without consideration of many factors.
And then when you go into the third party SDKs like Android and iOS and anything else, it is dozens if not hundreds more different parts, all tested to different levels.
It only takes one tiny part that doesn’t handle “weird” characters properly and it all fails. That is how software works. There is 100% and there is 0%. As a user, you should consider taking steps to ensure you get 100% rather than 0% functionality.
I inherited a project which uses the localization system so the addressable bundles were automatically named *_français_all.bundle. After a bit of flailing and digging around the project, I found that you could set the Bundle Naming Mode to Only Hash for example which you can use to work around the issue.
Not sure if that’s something that was wrongly configured in my case since I think that name was generated based on the culture info for that language. Happy to stand correct though
