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
- A submenu disappears on MacOS when the MenuItem method argument "isVariableFunction" is set to "false" and priority argument is set to "-1"
- The Sprite Library Editor window has an incorrect order of Sprites when the Sprites are reordered and the order saved
- Tilemap Tiles do not get lit up unless the Light Range is greater than the distance between the position of the Tile before the transformation and the Light Source when the Tile is transformed with Tilemap.SetTransformMatrix method
- The Editor and "Reloading Domain" windows are frozen when entering Play Mode
- Crash when attempting to create a custom FMOD DSP unit
Add comment