[0.8.4] Can't use "#" on any part of project path while using Fast or Virtual mode at editor

Unity Engine
1

Hello,

as title suggests having “#” on your project path will result in entire AddressablesSystem being unable to initialize at the editor, while using Play Mode Script Fast Mode or Virtual Mode.

Calling Addressables.InitializeAsync(); or any Load/Instantiate function will result in the following 2 messages being shown at the console and no asset being loaded successfully.

Addressables - runtime data operation completed with status = Failed, result = .
UnityEngine.AddressableAssets.Addressables:InitializeAsync()

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]].
UnityEngine.AddressableAssets.Addressables:InitializeAsync()
1 Like
2

Something about using # in a file path or file name feels very wrong to me. It seems like begging for trouble.

Ideally Unity ought to support things like this, but it’s also probably not a good idea to do rely on them even if they did. For example, let’s say you want to move that codebase into Perforce. Now you have wildcard characters in your file paths. Unity handled it for you on their end, but now your VCS is in the way.

1 Like
3

I agree with you and promptly renamed the directories, but its possible the same thing could happen with regular characters in other languages so I posted here for reference.

4

Apparently this is still an issue! Unfortunately I just ran into it, and wasted an entire day before figuring this out.

While I agree avoiding # in the path is a smart idea, it is a valid character for windows directory names, and I feel like Unity should support this (or at least through a better error!).