Support
Support & Status
Report a bug
In the app: Settings → Report a Bug. You can optionally attach your anonymized run log (timing and status of each API call only — never your email, password, diver ID, or location) to help diagnose the issue faster.
You can also email us directly — see the app's Settings screen for the current support address.
Current status
Checking…
The app checks this automatically before you submit a bug report, and shows a banner if there's something already known — so you're not the fifth person to report the same thing the same day.
A note on how FitDive works
FitDive isn't an official MySSI or Garmin integration — there's no public API for either. It works by using your own MySSI login the way a browser would, and by reading the structure of Garmin's .fit file format directly.
.fit format) could change in a way that breaks FitDive without warning. If that happens:
- We're usually able to tell quickly, because it breaks the same way for everyone.
- We treat it as a priority fix — this app doesn't work at all if the integration is broken, so there's no version of "good enough for now."
- We'll post here as soon as we know, and again once it's fixed.
We can't promise a fix time, since it depends on what changed on MySSI's end and whether they left us a way to adapt. But we will always be working on it, and this page is where you'll hear about it first.
What we can't help with
FitDive submits dives using the same fields MySSI's own "Add Dive" form uses. If a dive looks wrong inside MySSI after import, check the values FitDive showed you on the Review screen before you submitted — if those were right, the issue is downstream of FitDive and MySSI's own support is the right place to ask.