Post

Replies

Boosts

Views

Activity

Crash during App Review - We were unable to review your app as it crashed on launch
Hey, We are currently having an issue trying to distribute our app to App Store. We keep getting the same response from Apple and are trying our best to fix it. This is the error we are getting: Hello, The issues we previously identified still need your attention. If you have any questions, we are here to help. Reply to this message in App Store Connect and let us know. Guideline 2.1 - Performance - App Completeness We were unable to review your app as it crashed on launch. We have attached detailed crash logs to help troubleshoot this issue. Review device details: Device type: iPad Air (5th generation) OS version: iOS 17.3.1 Next Steps To address the crash in your app, follow these steps: Fully symbolicate the crash report. See Adding Identifiable Symbol Names to a Crash Report for an explanation of the symbolication process. Match the crash report to a common pattern. Based on the pattern, take specific actions to further investigate the crash. See Identifying the Cause of Common Crashes. Test your app on a device to ensure that it now runs as expected. Once you’ve addressed the crash, create and submit a new build to the App Store for review. Here are previous crashlogs. crashlog-4E555E01-86E8-4F9C-A91B-F3FE7AD8058A.txt crashlog-87621D1F-0675-47E8-BD64-7FA28350EE26.txt We can see it has something to do with a "PathProviderPlugin" and we have no clue where we are using it. We can only see it in generated files in xcode. We are having no problems downloading the app on physical iOS devices or emulators and we are not getting any crashes/errors either. We had people test our app in TestFlight without any problems either a few months ago. The only solution I've found on the internet is the problem only exists within iPads, so we tried to remove iPads, iMac and Apple Vision Pro from the desitations in xcode, but they still tested it on an iPad. We are in a bit of a hurry with releasing our app because we have users waiting since last week. Anyone have any idea what we are missing? Any input is appreciated and we hope to hear from you! Best regards, Steffen G.
6
1
2.3k
Mar ’24