Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
0
Found in
2019.3.0a6
Issue ID
1162626
Regression
No
[ARM64] When using Executable Only, Player crashes on launch.
This crash ONLY happens when using Executable Only build, and it depends on the Build Configuration:
- Master: Always launches
- Debug: Always crashes
- Release: Depends on how the previous Player settings. If the previous one is in Debug, this one crashes as well; if the previous one is in Master, this one launches without issue.
The crash happens before the Script Debugging window can appear for debugger being attached.
However, there is not issue in building or installation, just launching.
Repro:
1. Create a new or use an existing project
2. Set Build Settings to ARM64, ExecutableOnly
3. Build (Or Use Device Portal with Build and Run, depends on if the update is merged)
4. Run on ARM64 device
Actual: ARM64 crashes at launch when using Executable Only build.
Note: Attached error message is from Editor when using Device Portal for deployment.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Uninitialized variable warning appears in the Inspector of a custom shader when the variable is initialized
- "Failed creating toolbar element from ID..." error is thrown when resetting the Scene view Overlay layout while an Asset Transformer Toolbox overlay is active
- Entity ID for Font Assets is serialized twice which throws an error when using Debug Inspector
- Play Mode can be entered when disabling Adaptive Performance and pressing either the Play Mode button or the keyboard shortcut to enter Play Mode before recompilation leading to errors and warnings thrown
- Parent ListView element also becomes selected when inner ListView element is selected
Add comment