Location permission, destination selection, export format confusion, and support emails missing app version details.
Troubleshooting
Common RouteLocker issues and what to check first.
These steps focus on the most common support cases: speed readings, permissions, exports, backup and restore, and trip log behavior.
Unexpected restored data, missing trip segments, unusual speed updates, or issues that only occur on a specific iOS release.
Speed gauge is slow or not updating
- Confirm RouteLocker has active location permission.
- Check that you are moving and have usable GPS conditions.
- If the device just opened the app, wait briefly for location lock.
Trip logging did not behave as expected
- Review whether the trip was stopped manually or via auto-stop.
- Check whether the destination used for auto-stop was correctly selected.
- If needed, add or correct the entry manually. Expect an “M” marker after manual changes.
Saved location issues
- Verify the site was saved with the expected name and destination.
- Use search to add a fresh site entry if a saved one is outdated.
- Re-select the destination before relying on auto-stop.
Export confusion
- Choose CSV for broad spreadsheet compatibility.
- Choose XLS if your workflow expects that format directly.
- If an entry has an “M” marker, remember it was manually created or edited.
Restore concerns
- Restore only from a backup file you recognize.
- If restored data looks unexpected, note whether the issue existed before the restore.
- Contact support with version details and what changed after restore.
When to export a debug log
- Use it only when requested or when you want to provide extra troubleshooting detail.
- Export is manual and under your control.
- Review what you are sharing before sending it to support.
Still stuck?
Email support@seismic.place and include the RouteLocker version, iOS version, device model, and the exact step where the issue starts.