How to resolve apps crashing?
Short answerWhen apps crash across a whole crew, solve it at the fleet level rather than phone by phone. Set a minimum phone and operating system, pick one day a month to update everyone, keep a spare device in the truck, and ask staff to report crashes in one shared place. Patterns across devices show up quickly that way.
The explanation
A crew with mixed phones, some five years old, will have unpredictable crashes. Decide the oldest phone you will support, and replace the ones below it. That one rule removes a lot of mystery.
Update on a schedule. If everyone updates on the first Monday, you know the baseline and can compare. If one person updates early and another never does, a crash on one phone says little. Keep a spare phone or tablet in a truck so a crash does not stop a job.
Ask staff to post crashes in one thread with phone model and screen. After a month, you will see whether it is one model, one app version or one task such as uploading photos. Then you can raise it with the vendor with evidence rather than guesses.
Steps
- Set the oldest phone and operating system version you will support.
- Pick one day a month for everyone to update.
- Keep a spare device available for crashes in the field.
- Collect crashes in one thread with phone model and the screen involved.
What to watch for
- Letting every crew member decide on their own when to update.
- Reporting crashes to the vendor without the phone model.
How Apex does it
Not a scheduler feature
Apex has roles for crew and office users and installs as a web app on any modern phone browser. It is early access with a single business, so a fleet-level compatibility history across many phone models does not exist yet.
Apex Flow Scheduler is in early access. See how we label status.
Where this question comes from: owners type it, or a close variant, into search boxes. It was returned by public search suggestions (Google, Bing or DuckDuckGo) when we collected them on 2026-10-06. We do not have search volumes.