Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2019.4.X, 2020.3.X
Votes
0
Found in
2019.4
2019.4.24f1
2020.3
2021.1
2021.2
Issue ID
1330126
Regression
No
[iOS] Crash on ScriptingGCHandle::Acquire when calling RequestUserAuthorization without using yield for pending authorization
Steps to reproduce:
1. Open the project attached by the user
2. Build for iOS
3. Run the Xcode project on a device
Reproducible with: 2019.4.24f1, 2020.3.2f1, 2021.1.2f1, 2021.2.0a14
First five lines of the stacktrace:
frame #0: 0x00000001061a6df8 UnityFramework`ScriptingGCHandle::Acquire(ScriptingObjectPtr, ScriptingGCHandleWeakness) + 16
frame #1: 0x0000000106197ac4 UnityFramework`Application_Bindings::RequestUserAuthorization(int) + 52
frame #2: 0x0000000106630c90 UnityFramework`Test_Start_mA902842AF55C0A063D71F22B280F28BF0FB01497 + 224
Reproducible on:
- iPad 9.7" 6th gen (14.4)
- iPad Air 2 (11.0.3)
- iPhone XR (13.4.1)
- iPhone 8 Plus (12.0)
Notes:
- Case 1323715 (https://issuetracker.unity3d.com/product/unity/issues/guid/1323715/) produced the same stacktrace, but in that scenario yield was used to wait for pending request results
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note (fix version 2022.1):
Fixed in 2021.2.0a17
Resolution Note (fix version 2020.3):
Fixed in 2020.3.25f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.35f1