Skip to main content

Troubleshooting: app crashes

If Benchmrk crashes unexpectedly, this page covers common scenarios and steps to resolve them.

Common crash scenarios​

Crash on launch​

If the app crashes immediately after opening:

  1. Force-close and relaunch — swipe up from the bottom of the screen (or double-press the Home button), swipe the Benchmrk card away, then reopen the app.
  2. Restart your device — a device restart can resolve memory or system-level issues.
  3. Update the app — check the App Store for updates. Crashes may be fixed in a newer version.

Crash when opening AR view​

The AR view requires iOS 14.0+ and a physical device. Crashes may occur if:

  • Your device does not support AR geo-tracking.
  • Camera permission was denied.

Solution: Ensure your device meets the AR requirements and that camera permission is granted.

Crash when loading mark data​

If the app crashes when viewing mark details or search results:

  • The jurisdiction API may have returned unexpected data.
  • A large number of marks may be causing memory pressure.

Solution: Try zooming in to reduce the number of visible marks, or switch to a different area.

Crash during navigation​

Navigation crashes may occur due to:

  • Loss of GPS signal.
  • Memory pressure from the Mapbox Navigation SDK.

Solution: End the navigation session, close other apps to free memory, and try again.

Clearing cache​

If crashes persist, clearing the app's cached data may help:

  1. Delete the app from your device (long-press the app icon → Remove App → Delete App).
  2. Reinstall from the App Store.
  3. Sign in with your existing account — your account data is preserved.
info

Reinstalling the app clears all local data, including saved filter preferences. Your account and mark data are stored in the cloud and will be restored after signing in.

If crashes continue​

If the app continues to crash after trying the above steps:

  1. Ensure your device is running iOS 18.0 or later.
  2. Check that you have sufficient free storage on your device.
  3. Contact support via Profile → Support with details about when the crash occurs.
Was this page helpful?