Search Issue Tracker
Fixed
Fixed in 1.19.19
Votes
6
Found in [Package]
1.19.17
Issue ID
ADDR-2494
Regression
No
“Invalid path in AssetBundleProvider:." is thrown when loading an updated remote bundle for local static Assets
How to reproduce:
1. Open the user's attached "2077Demo.zip" project
2. Set the webserver address on line 131 in the "Launch.cs" script (webserver address can be found in the Addressables Hosting window)
3. Drag and drop "LobbyPanel" Addressable from "Content Update" group to "UI_Panel" group in the Addressables Groups window
4. Press Build >> New Build >> Default Build Script in the Addressables Groups window
5. Select "LobbyPanel" Addressable from the Addressables Groups window
6. Press "Open Prefab" in the Inspector window
7. Select and disable the "Text" Component in the Hierarchy window
8. Press Build >> Update a Previous Build in the Addressables Groups window
9. Select a build in the "Windows" folder to update
10. Enter Play Mode
Expected result: "Invalid path in AssetBundleProvider: '' error doesn't appear in the Console window
Actual result: "Invalid path in AssetBundleProvider: '' error appears in the Console window
Reproducible with: 1.19.9 (2019.4.36f1), 1.19.17 (2020.3.27f1, 2021.2.9f1, 2022.1.0b5, 2022.2.0a3)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment