User Profile

Posts

Posts

Post not yet marked as solved
2 Replies
1.8k Views

iOS 16 beta related crash - UIView UIDebugging Description UIGetCurrentFallbackTraitCollection

We have a handful of users with the iOS16 beta that are reporting app crash on launch. We're seeing this new crash which seemingly only impacts iOS 16 users, but the crash report doesn't seem to indicate a crash point in our app (only OS/system level objects). In the crash log, the main thread appears to be stuck in a loop with trait collections possibly leading to resource exhaustion/stack overflow, but I can't see where the stack begins within our app at all, everything in the log seems OS level. UPDATE: Started on 27 July 2022, which is the same release date as iOS 16 Beta 4 (20A5328h) - confirmed all crash reports are for this release of iOS 16 (20A5328h). Bug report logged https://feedbackassistant.apple.com/feedback/11079459 . Screenshot from Organizer and crash report below: 2022-08-05_11-06-29 - ios16 Crash Report.txt
Posted
by jarradcutting777.
Last updated
.
Post marked as solved
2 Replies
641 Views

Crash logs disappered "No crash logs"

Since XCode 13.1 I'm getting "no crash logs" error in my Organizer window. I have re-authenticated, changed the filters to be as broad as possible (ie all versions, all platforms, for the last year) - and I still get this error. I know there are crash logs because up until now (ie the past few weeks) I've been reviewing them! I've cleared derived data, I've cleaned the project, I've rebooted, I've closed and restarted xCode, I've opened XCode preferences and re-authenticated (I had recently changed password so it was prompting me to re-authenticate anyway). Still, no crash logs. Any other cached data I should be clearing that could fix this? I know I have crash logs piling up right now.
Posted
by jarradcutting777.
Last updated
.