Apple · app crashing

Apple iPad and iPad mini app keeps crashing, freezing or will not open

Apple iPad and iPad mini (10th generation and mini 6th generation) app keeps crashing, freezing or will not open: one app versus the operating system, storage and service state determines the safe sequence. Scoped to iPad (10th generation) and iPad mini (6th generation).

For the Apple iPad and iPad mini (10th generation and mini 6th generation), one app versus the operating system, storage and service state determines the safe sequence. First, establish the pattern before changing anything. Clear the app's cache first, then its data if that fails. Clearing data signs you out and discards local content, so it is the second step, not the first.

Differential

Likely causes of “Apple iPad and iPad mini app keeps crashing, freezing or will not open”, and how to tell them apart

  1. 1

    The app's stored data has become corrupt

    What separates it It crashes immediately on launch, every time, having worked before. Cache and stored state can be left inconsistent by an interrupted update or a full disk.

    How to confirm Clear the app's cache first, then its data if that fails. Clearing data signs you out and discards local content, so it is the second step, not the first.

  2. 2

    Storage is full or nearly full

    What separates it Several apps misbehave at once, updates fail, and the camera refuses to save. An app that cannot write cannot run reliably.

    How to confirm Check free storage before anything app-specific. Below a few percent free, all bets are off across the whole phone.

  3. 3

    The app version and the OS version disagree

    What separates it It broke immediately after an OS update, or after an app update on an older OS. Compatibility runs both ways.

    How to confirm Check for an app update, and check whether the app still supports your OS version. An app that has dropped support for your OS will not be fixed by reinstalling it.

  4. 4

    A permission it needs was revoked

    What separates it It crashes at one specific action — opening the camera, attaching a file, starting a call. An app given a hard denial where it expected access can fail rather than degrade.

    How to confirm Check the permissions for that app against what the failing action needs.

  5. 5

    A specific piece of content is triggering it

    What separates it It crashes on one conversation, one photo, one file, and is fine otherwise. A malformed item can take the app down every time it is rendered.

    How to confirm Note exactly what was on screen or being opened. A reproducible trigger is a report worth sending to the developer, and it is also avoidable in the meantime.

  6. 6

    The phone is out of memory

    What separates it Apps close in the background and have to reload constantly, worse with many apps open or during heavy use. This presents as apps 'restarting' rather than crashing.

    How to confirm Restart the phone and compare. Reloading rather than crashing is a memory symptom, not an app fault.

  7. 7

    A bad update from the developer

    What separates it It started for many people on the same date, and the app store reviews say so. Nothing on your phone caused it.

    How to confirm Check recent reviews and the developer's status channels before spending time on your own configuration.

  8. 8

    An account or sign-in state that cannot be resolved

    What separates it It crashes at the sign-in step or immediately after. A stale token can put the app into a state it cannot recover from.

    How to confirm Sign out and back in where possible before clearing data, since signing out is the lesser action.

  9. 9

    Overheating

    What separates it Crashes cluster during heavy use or in the sun, and stop when the phone cools. A throttling phone changes performance underneath the app.

    How to confirm Let it cool and retry the same action.

Before you touch a setting

Record this first — changing settings destroys the evidence

  • Whether it crashes on launch, at a specific action, or randomly during use. Those are three different faults.
  • Whether one app is affected or several, which separates an app problem from a phone problem.
  • The date it started, and what happened then: an OS update, an app update, a full disk, a new account.
  • Exactly what was on screen or being opened when it failed, since a reproducible trigger is the most valuable single fact.
  • Free storage on the phone.
  • The app version and the OS version.
  • Whether the phone was hot at the time.

Try in this order

0 of 9 completed
  1. Establish the pattern before changing anything

    Reversible

    Crashing on launch, at one specific action, or randomly are three different faults with three different fixes. Reinstalling first destroys the evidence that would have told you which one you had.

  2. Check free storage

    Reversible

    An app that cannot write cannot run reliably, and below a few percent free the whole phone misbehaves — several apps at once, failed updates, a camera that will not save. This is a phone-level cause that looks like an app-level one.

  3. Restart the phone

    Reversible

    Apps that reload constantly rather than crashing outright are describing memory pressure, not a defect. A restart clears it, and comparing before and after distinguishes the two in a couple of minutes.

  4. Check for an app update and an OS compatibility gap

    Reversible

    Compatibility runs both ways: an OS update can break an old app, and an app update can drop support for an old OS. An app that no longer supports your OS version will not be fixed by reinstalling it, which is where a lot of effort gets wasted.

  5. Check the permissions the failing action needs

    Reversible

    An app crashing at one specific action — opening the camera, attaching a file, starting a call — is frequently one that was given a hard denial where it expected access and did not handle it gracefully.

  6. Clear the cache before clearing data

    Signs you out

    Cache is disposable; data is your local content and your session. Clearing cache costs nothing and fixes a real share of corrupt-state crashes. Clearing data signs you out and discards what is stored locally, which is why it comes second.

  7. Check the app store reviews and the developer's status

    Reversible

    A crash that started for many people on the same date is a bad release, and nothing on your phone caused it or will fix it. Thirty seconds of reading prevents an afternoon of configuration.

  8. Note the exact trigger where one exists

    Reversible

    One conversation, one photo, one file that reliably takes the app down is the most valuable fact available — it is a report the developer can act on, and it is avoidable in the meantime.

  9. Reinstall last, and know what it costs

    Signs you out

    It clears everything local and re-prompts for permissions, which is why it sometimes works. It also discards anything not synced, and it teaches you nothing about the cause — so it belongs after the cheaper, more specific steps.

Model-specific

What is true of this model and not of its siblings

Model scope
iPad (10th generation) and iPad mini (6th generation). Apple iPad family; connector, cellular option, camera, biometric and iPadOS eligibility vary by exact model.
Hardware — Apple tech-specs article
10.9-inch Liquid Retina LCD (2360x1640, 60Hz), A14 Bionic chip, USB-C, supports only the 1st-gen Apple Pencil (via USB-C adapter) or the USB-C Apple Pencil — not the 2nd-gen Pencil or Pencil Pro.
Tier — entry iPad (A14)
The entry iPad (10th gen) with an A14 chip (not M-series), a Liquid Retina LCD and a USB-C port. iPadOS. Good for everyday use; it is not a Pro/Air performance tier, which is the price, not a fault.
Apple Pencil confusion — needs an adapter
A notorious quirk: the 10th-gen iPad supports the 1st-generation Apple Pencil (and the USB-C Pencil), but the 1st-gen Pencil charges via Lightning while the iPad has USB-C — so it requires the USB-C-to-Apple-Pencil ADAPTER to pair and charge. It does NOT work with the 2nd-gen Pencil or Apple Pencil Pro (no magnetic side charging).
Wi-Fi or Cellular
Wi-Fi or Wi-Fi+Cellular (eSIM); no signal on a Wi-Fi model is expected.
Symptom boundary
This record covers Apple iPad and iPad mini (10th generation and mini 6th generation) when it app keeps crashing, freezing or will not open. A different symptom on the same hardware, or this symptom on a different Apple product line, has its own record with its own causes and its own cited source.

Stop boundary

When this stops being a self-service repair

  • !Several unrelated apps crash after every step here, which points at the phone rather than any app.
  • !The app has dropped support for your OS version — no reinstall changes that, and the choice is the OS or the app.
  • !A reproducible crash on specific content, which is a developer matter and worth reporting with the exact trigger.
  • !The phone restarts itself rather than the app closing, which is a system-level fault.

Evidence ledger

Sources behind this answer

Exact questions

Common questions

My Apple Pencil won't pair with my 10th-gen iPad.+

The 10th-gen iPad only works with the 1st-generation Apple Pencil (or the USB-C Pencil), not the 2nd-gen Pencil or Apple Pencil Pro — and here is the catch: the 1st-gen Pencil has a Lightning connector, but this iPad has USB-C, so you need Apple's USB-C-to-Apple-Pencil adapter to connect and pair it. Without that adapter it cannot pair or charge. It also does not magnetically attach to the side for charging like the newer Pencils do.

Wrong device or version?

Match the path before repeating the steps.

Match another device