Search Issue Tracker
Not Reproducible
Votes
0
Found in [Package]
1.9.2
Issue ID
1254334
Regression
No
[iOS][Addressables] Loading an addressable scene causes the application to freeze when engine code stripping is turned on
How to reproduce:
1. Open the user-supplied project "unity-addressables-engine-stripping-bug.zip"
2. Build the "LoaderScene" Scene for iOS and launch it on a device
3. Tap the "Load addressable scene" button
Expected result: the Addressable scene loads
Actual result: the scene either does not load or freezes in the first frames and an error is thrown in Xcode
Reproducible with: 2018.4.24f1, 2019.4.2f1, 2020.1.0b14, 2020.2.0a16 (Addressables 1.9.2, 1.10.0)
Could not test with: Addressables 1.1.3-preview-1.8.4 due to a MissingMethodException
Reproduces on:
VLNQA00160 iPhone 6S iOS 13.3.1
Notes:
1. The full Xcode error:
Could not produce class with ID 95.
This could be caused by a class being stripped from the build even though it is needed. Try disabling 'Strip Engine Code' in Player Settings.
(Filename: Line: 1531)
GameObject contains a component type that is not recognized
(Filename: Line: 1012)
Unloading 4 Unused Serialized files (Serialized files now loaded: 2)
Could not produce class with ID 245.
This could be caused by a class being stripped from the build even though it is needed. Try disabling 'Strip Engine Code' in Player Settings.
(Filename: Line: 1531)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Increased Memory usage when Update Mode 'On Demand' Realtime lights are used and DX12 API is selected
- Shader warnings in URP ShaderGraph when using the Normal From Texture node
- 'Stack overflow' error logged in the Console when a script that has a lot of classes is compiled
- Memory Leak warnings are thrown when creating a new material
- The type selector in the UI Builder does not display primitive types when trying to select one in the "Select Type…" window
Add comment