Post

Replies

Boosts

Views

Activity

Reply to App crash: Inconsistency in UITabBar items and view controllers detected. No view controller matches the UITabBarItem.
Thanks for you response. The issue ended up being that we had mistakenly created 2 UITabBarController instances and moved the child viewcontrollers over to the one that wasn't being displayed. The crash occurred when a tab bar item was tapped and the associated viewcontroller was referencing the other UITabBarController instance.
Topic: UI Frameworks SubTopic: UIKit
Jul ’24
Reply to App crashes: CA::Render::InterpolatedFunction::encode(CA::Render::Encoder*)
Here's a full crash report: crash_report.txt
Topic: UI Frameworks SubTopic: General Tags:
Replies
Boosts
Views
Activity
Dec ’23
Reply to App crashes: CA::Render::InterpolatedFunction::encode(CA::Render::Encoder*)
In case this is helpful for anyone, I got this response from Apple: Looking through your crash logs the cause appears to be related to the use of gradient layers. This is either causing a memory allocation error or some other problem in your app. Please review your use of gradient layers.
Topic: UI Frameworks SubTopic: General Tags:
Replies
Boosts
Views
Activity
Jan ’24
Reply to App crash: Inconsistency in UITabBar items and view controllers detected. No view controller matches the UITabBarItem.
Thanks for you response. The issue ended up being that we had mistakenly created 2 UITabBarController instances and moved the child viewcontrollers over to the one that wasn't being displayed. The crash occurred when a tab bar item was tapped and the associated viewcontroller was referencing the other UITabBarController instance.
Topic: UI Frameworks SubTopic: UIKit
Replies
Boosts
Views
Activity
Jul ’24
Reply to App crash when using SwiftUI view in UICollectionView
Attaching a crash report: 2024-12-02_21-50-20.3400_-1000-eb116a1c71b8d354e66d6ecfc079873406aefab4.crash
Topic: UI Frameworks SubTopic: SwiftUI Tags:
Replies
Boosts
Views
Activity
Dec ’24