Search Issue Tracker
Fixed in 2018.3.X
Votes
0
Found in
2017.2.1f1
Issue ID
997468
Regression
No
[iOS] Player crashes at ActivateAwakeRecursivelyInternal() when loading scene from bundle
To reproduce:
1. Open user's attached project
2. Make sure that "bootstrap" scene is opened
3. In the menu bar, click Build -> iOS Player
4. Launch built project on the device
5. Hit "Next Scene" button
Expected result: Scene from the bundle is loaded successfully.
Actual result: Player crashes
Reproduced with: Unity 2017.1.3p1, 2017.2.1f1, 2017.3.1p1, 2018.1.0b7, 2018.2.0a1
Device: iPhone 7+ iOS 11.2.5
Resolution:
This is a known limitation. A user has to hint that a specific component is used in the main app.
- If a component has scripting counterpart just by adding it to link.xml or unused C# script field.
- If it’s only available as Unity component then including an extra semi-empty scene that references all used components works as a hint.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
Add comment