Broken by an update

App Not Working After an iOS Update: Prove the Cause, Rebuild With Current Tools, Ship the Repair

Nobody touched the code. Nobody shipped a build. And since the weekend, the support emails keep starting with the words "since I updated my phone." The app did not change. The ground under it did.

November 19, 2026 · 9 min read

acmegrocerydelivery.com · crash reports by iOS version
Five days after a new iOS release reached phones
The crash lives only on the newest iOS
Sample
Newest iOS release412 reports
Previous release17 reports
Two releases back9 reports
Older versions3 reports
Illustrative: sample crash breakdown for a fictional grocery delivery app

The short answer

If your app stopped working after an iOS update, first prove the update is the cause by comparing crash reports and failures by iOS version and testing on a phone running the new release. Then rebuild with current Xcode tools, replace code that relied on old behavior, test through TestFlight and submit. Apple says bug fixes for live apps are not delayed over guideline violations except legal or safety ones.

On this page
  1. Nobody touched the code, and that is the whole problem
  2. Prove it was the update before you blame it
  3. The hour after the update lands on customers' phones
  4. What tends to give way when the operating system moves
  5. Rebuild with today's tools, then test like a skeptic
  6. Sending the rebuild to Apple without a second delay
  7. Next year's update, and who to call about this one

Nobody touched the code, and that is the whole problem

An iPhone app is a guest in someone else's house. Apple owns the house and rearranges the furniture on its own schedule. Code written two years ago made assumptions about how the system would behave, which calls it could make and how screens would be drawn. Most of those assumptions still hold after an update. One that does not is enough to stop a checkout, freeze a login or close the app on launch.

This page covers the emergency version: the update reached your customers' phones and something broke. The chronic version, an app nobody has maintained in years, is a rescue job for our fixing broken mobile apps team. If the app simply dies on open with no update involved, start at iOS app crashing. Everything else in the emergency repair section follows the same rule you will see below: prove the cause before you fix it.

We say nothing here about what any particular iOS release changed. That is not modesty; it is discipline. Release notes are long, forum threads are confident, and the only reliable answer about your app comes from your app, running on the new version, on a desk in front of someone who can read what it says.

Prove it was the update before you blame it

Updates make convenient villains. They arrive with a date, a version number and a news cycle, so every problem that week gets pinned on them. Sometimes that is right. Sometimes the real cause was a server deploy on the same Tuesday. Twenty minutes of sorting saves a day of fixing the wrong thing.

Bright blue duotone image of a smartphone with a blank screen tilted on its side, surrounded by solid circles, triangles and a thick diagonal stripe
The phone changed underneath the app, so the test starts on a phone running the new version.
Telling an iOS update problem apart from your own change
What you seePoints to the iOS updatePoints to something you changed
Who is affectedOnly customers on the new iOS version, across all app versionsCustomers on every iOS version, starting at one moment
When it beganClimbing over days as phones updateA cliff at a single hour
Crash reportsNew crash signatures appear only on the new OSNew signatures on every OS, matching a build or deploy
Your own test phoneBreaks after you update it; an older phone still worksBreaks on every phone you own
Server logsNormalErrors that start at the same time as the complaints

Apple's crash reports documentation, read in November 2026, says TestFlight and the App Store collect crash reports "for every submitted version of your app," and Xcode's Crashes organizer is where they appear. Sort them by operating system version. A crash that lives only on the newest iOS is the update's fingerprint. A crash that appears everywhere at once is usually yours, and our page on a failed software update covers rolling back your own change.

The hour after the update lands on customers' phones

  1. 1

    Update one test phone, keep one old

    Put the new iOS on one device and leave another on the previous version. The pair is your control group, and it settles arguments fast.

  2. 2

    Reproduce the complaint exactly

    Follow a real customer's path on the updated phone: install, sign in, the feature they named. Write down each tap and what happens.

  3. 3

    Sort crash reports by iOS version

    In the Crashes organizer, check whether the new signatures appear only on the new release. Save those reports outside Xcode.

  4. 4

    Check every outside service the feature uses

    Payments, maps, sign-in providers, your own API. If one changed the same week, test it separately before you blame the phone.

  5. 5

    Tell customers something true

    A short note that you know, you are working on it, and which iOS versions are affected. No dates you cannot keep.

  6. 6

    Decide who rebuilds

    If your developer can open the project in current Xcode today, start the rebuild. If nobody can, that is the moment to bring in help.

That last step catches more businesses than any bug. The project may not even open in current tools, because the last person to build it did so years ago on a laptop that no longer exists. Finding that out at minute fifty is far better than at hour six.

What tends to give way when the operating system moves

Calls marked deprecated years ago

Code that leaned on older system calls can keep working for a long time and then change behavior. The build warnings your team skipped are often the list of suspects.

Screens and layouts

Interface changes can clip text, hide a button below the fold or break a custom control that drew itself by hand.

Permissions and privacy prompts

Features that depend on location, photos, contacts or notifications break quietly when a permission arrives at a different moment than the code expects.

Third-party libraries

An analytics or payments SDK compiled for the old system may misbehave on the new one until its maker ships an update and you rebuild with it.

Push and server trust

Some breaks live on Apple's servers, not the phone. Apple announced in October 2024 that the certificate authority for push notifications would change on its servers in January and February 2025, as our push notifications stopped page records.

Login flows

Sign-in that opens a web view or hands off to another app is a common casualty. The app login broken page covers that path.

These are patterns from practice, not a list of what any specific release did. The point of naming them is to give the person reading your crash reports somewhere to look first. Signing is the other quiet suspect: Apple's certificates overview, read in November 2026, notes that "Apple can revoke digital certificates at any time at its sole discretion." If launch fails with nothing in the organizer, read our page on expired Apple certificates too.

Rebuild with today's tools, then test like a skeptic

The fix for most update breakage is not a patch on the old build. It is a rebuild: open the project in the current version of Xcode, compile against the current software development kit, read every warning, and replace the code that relied on old behavior. Then test it on the phones your customers carry. Apple's App Review page, read in November 2026, gives the advice in one line: "Make sure to thoroughly test on devices running the latest software and fix all bugs before submitting."

TestFlight is how you test with real people before the public sees the build. Apple's TestFlight page, read in November 2026, allows up to 100 internal testers and says "You can also invite up to 10,000 external testers to join your beta program," as of November 2026. External testing needs the first build "approved by App Review for TestFlight." For an emergency, a handful of internal testers on the new iOS, plus a few on the old one, is usually the right size.

Sending the rebuild to Apple without a second delay

Apple's App Review Guidelines, last updated October 16, 2026, contain a line worth knowing in this situation: "For apps that are already on the App Store or alternative distribution, bug fixes will not be delayed over guideline violations except for those related to legal or safety issues." A compatibility repair for a live app is a bug fix. Keep the submission to the repair, so that is all it is.

If the breakage stops customers from using the app at all, Apple's App Review page describes expedited review for extenuating circumstances such as a critical bug, and asks for steps to reproduce it on the current version. Request it once, honestly, with the device and iOS version in the steps. Typical review times, and what to do if the rebuild is rejected, are on our App Store rejection page. No one can promise you an approval or a date.

  • Submit the repair alone, without the new feature marketing wanted to sneak in.
  • Write review notes that say what broke, on which iOS version, and what the build changes.
  • Keep the demo account working and the server switched on during review.
  • Tell support the honest status: fixed, submitted, waiting on Apple.

Next year's update, and who to call about this one

The cheapest repair is the one done before customers notice. Test the app on each new iOS version as soon as your team can get it onto a spare phone, keep the project building in current Xcode a few times a year, and treat build warnings as maintenance tickets rather than background noise. That habit costs a few hours a year. The alternative costs a launch week.

Handle it yourselves when your developer can open the project in current Xcode, reproduce the break and test the rebuild this week. Call us when nobody can build the project, when the original developer is gone (our developer disappeared page lists what to recover), or when the break sits in payments or login. DataCram responds the same business day during the hours on our contact page.

Emergency mobile work starts from $575, depending on complexity, with a written estimate before work starts. The emergency app repair offer explains the access we need, and emergency pricing explains what moves the estimate. Longer modernization belongs with our iOS app development team, and an app that should exist on both platforms is a mobile app development conversation. We are a San Antonio studio building for the web since 1999; see our work or call (210) 346-0848.

Questions owners ask in an emergency

Usually because the code relied on behavior the new version changed: an older system call, a layout, a permission prompt, or a third-party library built for the old system. The crash reports, sorted by iOS version, show where. Test on a phone running the new release next to one that is not.

Compare who is affected. Problems limited to customers on the new iOS version, growing as phones update, point to the update. Problems on every iOS version, starting at one hour, point to your own release or server. Xcode's Crashes organizer lets you separate reports by operating system.

Most compatibility problems are fixed by rebuilding the project in current Xcode against the current development kit, fixing the warnings and replacing code that relied on old behavior. A small server-side change can sometimes work around it in the meantime, but the lasting fix usually ships as a new build.

Apple's guidelines say bug fixes for apps already on the store will not be delayed over guideline violations except those related to legal or safety issues. Keep the submission limited to the repair. Apple still reviews it, and no one can promise approval or a date.

Rarely, if the code itself is incompatible, and reinstalling can erase data stored only on the phone. Ask customers to wait for the update instead, and tell them which iOS versions are affected. The real repair is a new build tested on the new release.

DataCram's emergency mobile work starts from $575, depending on complexity, with a written estimate before work starts. A project that no longer opens in current tools takes more work than a single broken screen, and the estimate says so before anything begins.

Keep reading

Free · No obligation

Find out what the update broke

Tell us which iOS version, which feature and when the complaints started. Someone at DataCram replies the same business day with what we need to reproduce it and a written estimate.

Which of these sounds like you? (pick any)

Rather talk now? Call (210) 346-0848.

CallGet a quote