Search Issue Tracker
Won't Fix
Votes
0
Found in
5.6.0f3
Issue ID
917050
Regression
No
[iOS] [Simulator] Crash at "dyld`__abort_with_payload" when application is started
Reproduction steps:
1. Open the attached "Archive" project.
2. Build and run it for iOS (Simulator SDK).
- Application crashes:
* thread #1, stop reason = signal SIGABRT
* frame #0: 0x000000010f1cc9ee dyld`__abort_with_payload + 10
frame #1: 0x000000010f1cc43b dyld`abort_with_payload_wrapper_internal + 90
frame #2: 0x000000010f1cc464 dyld`abort_with_payload + 9
frame #3: 0x0000000103ae9bad dyld_sim`abort_with_payload + 34
frame #4: 0x0000000103ae2a7b dyld_sim`dyld::halt(char const*) + 354
frame #5: 0x0000000103ae4857 dyld_sim`dyld::_main(macho_header const*, unsigned long, int, char const**, char const**, char const**, unsigned long*) + 3669
frame #6: 0x0000000103ae0238 dyld_sim`start_sim + 136
frame #7: 0x000000010f1aa510 dyld`dyld::useSimulatorDyld(int, macho_header const*, char const*, int, char const**, char const**, char const**, unsigned long*, unsigned long*) + 2246
frame #8: 0x000000010f1a8a39 dyld`dyld::_main(macho_header const*, unsigned long, int, char const**, char const**, char const**, unsigned long*) + 241
frame #9: 0x000000010f1a4249 dyld`dyldbootstrap::start(macho_header const*, int, char const**, long, macho_header const*, unsigned long*) + 470
frame #10: 0x000000010f1a4036 dyld`_dyld_start + 54
Reproduced with:
5.6.0b1, 2017.2.0a2
iOS 9.3, iOS 10.3
RESOLUTION: WONTFIX. The issue is caused by Vuforia plugin not having iOS Simulator support. The libVuforiaUnityPlayer.a plugin only has arm64 and armv7 architectures. Please contact the plugin vendor for iOS Simulator support.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment