Laply support
Email hello@laply.app and a person answers. There is no ticket portal and no account to log into. For a race-day problem, the three things below are usually enough to work out what went wrong.
Email Laply supportWhat to send
- Device and OS iPhone 14, iOS 18.2 — the model matters more than you would think
- What the screen said The exact wording, or a screenshot if you still have the screen
- When it happened Roughly how far into the race, and whether the app had been backgrounded
Common issues
Four things that can go wrong during or just after a race, and what to do about each. Laply reached the App Store on 27 August 2026, so this list still comes from the app's own failure paths rather than from a support inbox — it gets rewritten from real reports as they arrive.
A race did not save
The race complete screen shows saving, saved, or failed. If it failed, the race stays on screen so you can retry before starting a new one. Tell us the device and what the screen said.
The app restarted mid-race
Laply keeps a copy of a live race on the phone and puts it back when you reopen the app, provided it can read that copy in full. If a race did not come back, tell us the device model and how far into the race it closed.
A lap was tapped by mistake
Undo the last lap tap from the active race screen. If a race is already saved, edit the runner or lap times from history and record the reason — the race keeps a correction count.
A roster import was rejected
Laply can only load backup files it saved itself, so a spreadsheet or a list from another app will not work. It also skips entries that are already in your roster or have no name. The summary after an import tells you what came in and what was skipped.