Search Issue Tracker
Active
Votes
0
Found in
2021.3.18f1
2022.2.5f1
2023.1.0b2
2023.2.0a3
Issue ID
UUM-27635
Regression
No
[Addressables] Exception is being thrown when Addressables.UpdateCatalogs is being called
Reproduction steps:
1. Open the attached project “SampleProject”
2. In the project, navigate to “Assets/Scenes” and open “TestScene”
3. Open the Build Settings and switch to either of the 3 build targets reported (MacOS, Android, or iOS)
4. Enable the Development Build option in the Build Settings
5. Make a build
6. Deploy to your chosen device
7. Connect the Unity Console to the application (for Android use Android Studio, for iOS use Xcode)
8. In the application, you should see 2 buttons. “Run Test” and “Stop Test”. Press the “Run Test” button, give it a few seconds then click “Stop Test”
9. Look at the Application log
Expected result: The catalog update would be attempted without issue
Actual result: The catalog update fails with an exception that seems to suggest it cannot find the path to the cache
Reproducible with: 2021.3.18f1, 2022.2.5f1, 2023.1.0b2, 2023.2.0a3
Could not test with: 2020.3.42f1 (Feature 'target-typed object creation' is not available in C# 8.0)
Reproducible on: MacOS 12.2.1 (Intel)
Notes:
1) If you wish to reproduce again, you shall need to uninstall and reinstall the application again
2) When building with Android, the build may fail on point d with a message saying the build is unsigned. If this happens, navigate to "Project Settings -> Player -> Publishing Settings" and set up a keystore which you can then sign with a password. Following this, you should be able to build.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment