Help for owners
My app works on Android but crashes on iPhone
Short answer
When an app crashes only on iPhone, the cause is almost always in the iPhone build or in something Apple treats differently: signing, permissions, the iOS version or a plugin. Gather the iPhone model, iOS version and app version, ask for a crash report from TestFlight or App Store Connect, and do not republish blindly.
Does this sound like your situation?
- The app opens on Android and closes by itself on an iPhone.
- It crashes as soon as it opens, before any screen shows.
- It crashes only when a feature is used, such as the camera, photos, location or notifications.
- Only some iPhones or iOS versions have the problem.
- A tester on TestFlight reports a crash but I cannot reproduce it.
Why does this happen?
The two builds are different programs
Even with shared code, an iPhone app is built, signed and packaged separately from the Android one. A fault can exist in one build only, for example a plugin that works on Android and is not set up on iOS.
The crash report tells you where
Apple says TestFlight and the App Store collect crash reports for submitted versions of your app. TestFlight users share them automatically, while for App Store users the Organizer only shows reports from customers who opted in to sharing diagnostics. Without a report, the fix is guesswork.
Confirmed by developer.apple.com
Apple expects a finished app
Apple's review guidelines are what every submitted version is judged against, so a build that crashes on iPhone should be fixed before it is sent in again.
Confirmed by developer.apple.com
Missing permission texts or capabilities
iOS asks for a written reason before an app uses the camera, location or photos, and a missing one can stop the app. The same goes for signing details such as the App ID and provisioning profile.
Technical detail: Xcode says the profile does not include your signing certificate
A newer iOS version changed something
An update to iOS can change how a system feature behaves. If the crash started after an iPhone update, that is the first thing to check.
What can I do about it today?
- Write down the exact device and versionsiPhone model, iOS version, app version and what the person was doing. Ask two or three affected users for the same.
- Find out how the app reached the phoneFrom the App Store, TestFlight or another way? It decides where crash reports are collected.
- Ask your developer for the crash reportCrash reports from TestFlight and App Store users are available to your developer in Xcode's Organizer. Ask for the one that matches your case.
- Try the other iPhones you haveDoes it crash on a newer or older iPhone? On an older iOS version? Note the difference.
- Do not push a new version in a hurryAnother untested release can add problems and a new round of review. Wait until the cause is known.
- Tell customers honestly if it mattersA short message that iPhone users are affected and a fix is being worked on keeps trust better than silence.
When should I bring someone in?
- The app crashes at startup for every iPhone user.
- The crash started after you released an update or after iOS changed.
- Your developer cannot produce a crash report or reproduce the problem.
How do I handle it?
- Collect the evidenceI read the crash reports and group them by iOS version and device, so I see whether it is one fault or several.
- Reproduce it on a real iPhoneI run the same build on matching hardware and follow the steps from the report.
- Fix the cause, not the symptomPlugin set-up, permissions, signing or an OS change is repaired where it began.
- Test both platformsThe fix is checked on iPhone and Android, since shared code can break the working side.
- Release through a test build firstThe corrected build goes to testers before it is sent for review, with a tested rollback ready.
The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.
What do owners ask about this?
Why does it work on Android then?
The two apps are built and run differently. A plugin, a setting or a permission can be correct on one and missing or broken on the other.
Can you fix it without seeing the crash report?
Reports make it faster and more certain. Without one I would need to reproduce the crash on a real device.
Is it Apple's fault?
Sometimes an iOS update exposes a weakness in the app. The app is still what has to be updated, so the fix is on your side.
Will fixing it need a new store review?
A change to the app means a new version, which goes through Apple review. Review time is Apple's, so I cannot promise it.
Sources
How was this page made?
I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.