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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
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