Help for owners
My app looks wrong on new iPhones and has not been updated for the latest iOS
Short answer
New iPhones change the screen shape and new iOS versions change how apps are drawn, so an app built for older ones can show cut-off buttons or content under the top and bottom areas. Apple also asks for uploads to be built with a recent Xcode, so a rebuild is part of the fix.
Does this sound like your situation?
- Buttons or text are cut off or sit under the top of the screen.
- The bottom menu overlaps the home indicator area.
- The app looks stretched or has black bars on a new iPhone.
- App Store Connect refuses my upload because the build is too old.
Why does this happen?
The layout was built for fixed sizes
If screens were designed for particular phones, a new size breaks them. Layouts that adapt to the space they get, and respect the safe areas, survive new devices.
The app was built with an old toolchain
Apple publishes requirements for what uploaded apps must be built with. At the time I checked, Apple required apps uploaded to App Store Connect to be built with Xcode 26 or later. Apple's page lists the current rule.
Confirmed by developer.apple.com
A framework or plugin is too old
Older third-party libraries can fail to compile with the newer toolchain, or draw wrongly on new system versions. They have to be updated with the app.
Technical detail: pod install cannot pick a version of a pod that satisfies every requirement
Nobody has owned updates since launch
Many apps are launched and left. The first time anyone notices is when a new phone or a store rule arrives.
What can I do about it today?
- Collect screenshots from real new phonesAsk a few customers or staff with the newest iPhones for screenshots of the screens that look wrong. Note the phone model and iOS version.
- Read the message from Apple, if there was oneForward the email or screenshot of the App Store Connect warning to your developer, unchanged.
- Find out who can build the appCheck you have the source code and the Apple Developer account in your own name. Without them nobody can ship an update.
- List the screens that matterLogin, the main action and payment. Those are the ones to repair first.
- Do not change the store listing in a hurryScreenshots and text can wait. A rushed change may start a new review while the real problem is still there.
When should I bring someone in?
- Apple has blocked an upload or an update because of the build tools.
- Key screens are unusable on current phones.
- No one has the source code, or the developer account belongs to someone else.
How do I handle it?
- Audit the screens on current devicesI run the app on current device sizes and note every screen that breaks.
- Update the toolchain and librariesI update the build tools and the libraries that block it, one at a time, and keep the old version safe in the repository.
- Fix layouts for adaptive sizesI replace fixed sizes with layouts that adapt and respect safe areas, so the next phone does not break it again.
- Release carefullyI prepare the build for review, test it on real devices and tell you what to expect. Review timing is Apple's decision, so I do not promise a date.
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?
Do I need a new app?
Usually not. Most of the time the existing app is updated and rebuilt, not rewritten.
Will the update be approved by Apple?
I prepare it to meet the published requirements, but the review is Apple's decision.
Do I have to keep updating the app?
Plan for regular updates, since Apple's requirements change. Their upcoming requirements page lists what is coming.
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.
For your developer: the technical fixes
building for 'iOS-simulator', but linking in object file (…) built for 'iOS'Simulator build fails because a library was built for real iPhones[!] CocoaPods could not find compatible versions for pod "FirebaseAuth":pod install cannot pick a version of a pod that satisfies every requirementMissing package product 'MyLibrary'Xcode reports a Swift package product as missing