Search Issue Tracker
Fixed
Fixed in 2021.3.55f1, 2022.3.63f1
Votes
0
Found in
2021.3.52f1
2022.3.62f1
Issue ID
UUM-105560
Regression
No
[iOS] Application frequently crashes on Social.LoadAchievements call when many achievements are registered
Reproduction steps:
1. Have an app in App Store Connect with 149 achievements (maximum limit)
2. Open the attached “iOS Achievement Crash” project
3. Build the project for the iOS platform
4. Run the built Xcode project on a iOS device
5. On the device, click the black square at the bottom of the screen
Expected result: The app continues to work
Actual result: The app crashes and “EXC_BAD_ACCESS” error is shown in Xcode
Reproducible with: 2021.3.52f1, 2022.3.62f1
Couldn't test with: 6000.0.49f1, 6000.1.4f1, 6000.2.0b2 (Social method group is obsolete in these versions)
Testing environment: macOS Sequoia 15.4.1 (M1 Max)
Reproducible with these devices:
VLNQA00624, iPhone 16 Pro, iOS: 18.3.1, CPU: Apple A18 Pro
VLNQA00394, iPhone 13 mini, iOS: 18.1, CPU: Apple A15 Bionic
Note: In step 5, you may need to click the black square multiple times for the crash to occur
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note (fix version 2022.3.63f1):
Fixed
Resolution Note (fix version 2021.3.55f1):
Fixed