Troubleshooting

Fixes for the problems that come up most often. Where something is a current limitation rather than a fault, this page says so instead of sending you round in circles.

I can't log in

Applies to: Apps and browser

Work through these in order — they are arranged by how common the cause is, not by how hard the fix is.

1. "Invalid login credentials"

This message means the email and password did not match an account. It does not mean the account is locked. Check for a typo, then reset the password:

  1. On the login screen, tap Forgot Password?
  2. Enter the email address associated with your account.
  3. Tap Send Reset Link.
  4. Check your inbox — and your spam folder, which is where it usually is.
  5. Follow the link, set a new password, and return to the app to sign in.

If the reset email does not arrive within a few minutes, the most likely cause is that the address you typed is not the one on the account. Ask whoever invited you (your gym owner, your trainer, or your admin) which address they used.

2. The security check never completes

Sign-in is protected by a Cloudflare Turnstile check. It normally passes without you doing anything. If it spins indefinitely or reports a domain error:

  1. Check that you have a working connection — the check is a network call.
  2. Disable a VPN or strict content blocker temporarily. Both can block the challenge without showing you an error.
  3. Close the app fully and reopen it. The challenge does not resume; it needs a fresh attempt.

If you get an explicit captcha or domain not authorized error rather than a silent hang, that is a configuration fault on our side, not something you can fix. Email support@mytraineros.com and quote the error text exactly. The support form is behind sign-in, so it is closed to you until you can log in.

3. You are signed in on another device and expected to stay signed in here

Signing in is per device: signing in on your phone does not sign you in in a browser. Signing out is not. Sign Out on one device ends your session on every device, and the others are signed out the next time they renew their session. The automatic log-off after a period without activity is the same Sign Out, so it ends your session on your other devices too.

Still stuck

Email support@mytraineros.com, or write to us from mytraineros.com/contact, with: the exact error text, whether you are on iOS, Android or a web browser, the email address you are trying (not the password), and whether it has ever worked on this device. The support form is behind sign-in, so it is no use for this problem.

I'm not getting notifications

Applies to: Apps and browser

Known limitation

Push notifications do not currently arrive on ANY platform — not iPhone, not iPad, not Android, not the web. This is our defect, not a setting on your device. The app never registers your device to receive push at all, so there is nothing you can grant, toggle, reinstall or reconfigure that will change it. In-app notifications work normally; open the app to see what you have missed.

Read the note above first, because it makes almost everything people normally try irrelevant.

Push does not work on any platform

This is worth stating plainly, because the honest answer saves you an afternoon: no device currently receives push notifications from MyTrainerOS. Not iPhone, not Android. The step where the app registers your device to receive push never runs, so your device is never registered — and a notification cannot be delivered to a device the system does not know about.

That means none of the following will help, and we would rather you did not spend time on them:

  • Granting or re-granting notification permission.
  • Reinstalling the app.
  • Signing out and back in.
  • Excluding MyTrainerOS from battery optimisation.
  • Turning notification categories on and off.

Earlier versions of this article gave an Android self-diagnosis checklist including all of those, and told you that opening Settings → Notifications would register your device. That was wrong. That screen saves your preferences; it does not ask for permission and it does not register anything.

One consequence worth knowing

The Push notifications toggle in your notification settings saves fine, and turning it on does not make push start working. It records what you want to receive, ready for when delivery is fixed. If you switched it on and nothing changed, the toggle is not broken — the delivery behind it is not there yet.

What still works

In-app notifications are unaffected. Open the app and you will see what you have missed. If something is genuinely time-critical — a session starting shortly, a payment that failed — check in the app rather than waiting to be told.

In a web browser

There is no browser push channel, and there was never going to be one. That part is by design rather than a defect.

Quiet hours

A push raised during your quiet hours (Settings → Notifications → Quiet hours) is not sent, and it is not sent later either. The notification is still listed in the app, under the bell at the top of the screen. Urgent notifications, such as a session request, and the ones the Notifications screen marks Always on are not held back by quiet hours. None of this changes what reaches your device today: as said above, no push is delivered to any device.

Should you file a ticket?

Not for "I get no push notifications" on its own — it is a known defect and it is on us. Do file one if you missed something that mattered, so we know who to tell when it is fixed, and tell us which notification you expected and when.

My data isn't syncing

Applies to: Apps and browser

Known limitation

If you edit a logged set offline and the same set is changed somewhere else before you reconnect, your offline edit is uploaded on reconnect and replaces the other change, and nobody is told. Avoid editing a set offline when someone else may be changing it too. Separately, most screens need a connection to load; the few that read from the device are named below.

What offline support actually covers today: logging new things — workouts, sets, meals and messages. Those are stored on the device and uploaded when you reconnect, with automatic retries. Most screens need a connection to load. These are read from the device when there is none: the exercise library and a workout, if each was opened on that device while connected, and the day's nutrition totals for meals logged on that device.

If something you logged is missing on another device

  1. Open the app on the device where you entered it, with a working connection, and leave it in the foreground for a few seconds. A queued change cannot upload from an app that is closed.
  2. Check the banner on that device. Offline it reads "Offline — N changes will sync when reconnected". Once connected it reads "Syncing N changes..." while the upload runs. No banner does not prove that everything uploaded: a change the server refused, or that failed five times, is no longer counted. When you return to the app it says "N changes couldn't sync — tap Settings to retry", but Settings has no retry control today, so that change stays on the device and is not sent again. Signing out removes it from the device.
  3. Pull down to refresh on the device where the data is missing.
  4. Check the device clock is set to automatic. A clock that is significantly wrong causes problems that look like sync failures.

If the app says some changes couldn't sync

When the app cannot get a change into your account, because the server refused it or five attempts failed, it stops trying on its own and tells you: "2 changes couldn't sync — tap Settings to retry". Open Settings. A card at the top, under your name, shows how many changes are affected, and its Retry sync button sends them again. The card then says what happened to each one: synced, still not synced, or waiting to be tried again. If someone else changed the same item in the meantime, their newer version is kept and the card tells you your change was not sent. The card is only there while something has failed. The changes stay on the device until they sync or you sign out, so retry before you sign out.

Do not fully trust the "Back online — N changes synced" message

N is the number of changes that left the pending count, and a change the server refused leaves it too. If something matters, check that it appears on the other device rather than relying on the message.

Large logs

A long workout can take a few seconds to appear on a second device. That is latency, not loss.

If data is genuinely lost

File a ticket before re-entering it, and say which device it was entered on, roughly when, whether that device was online at the time, and whether anyone else may have edited the same record. Re-entering first is understandable, but it makes the original problem much harder to find.

A payment was declined

Applies to: Apps and browser

Known limitation

The Manage Billing button on My Subscription, the member screen, does not open a billing portal for any member today, whether or not they have been charged: it shows "Something went wrong on our end. Try again in a moment." Contact your trainer or gym instead. Account owners open the billing portal for their MyTrainerOS plan in a browser only: Settings → Billing & Plan → Manage billing & invoices. The phone and tablet apps show the plan and have no billing button. Also: MyTrainerOS does not currently email members when a card declines — any decline notice you receive comes from Stripe.

Card declines are decided by the bank, not by MyTrainerOS. When a payment on a member's subscription to a trainer or gym fails, we are told that it failed and the bank's reason code, and the trainer's notice gives that reason in plain words, for example not enough funds or an expired card. When the bank gives no specific reason, the notice reads as a plain decline. When an autopay contract charge fails, the trainer's notice gives the amount owed and no reason. The member is sent neither notice, so the steps below start at your bank.

If a one-off payment was declined

  1. Check the card details — number, expiry, CVC, and especially the billing postcode, which is the most common silent mismatch.
  2. Check with your bank. Many banks decline a first payment to a new merchant and then approve the same card on a second attempt once you confirm it was you.
  3. Try a different card to establish whether the problem is the card or the transaction.

If a subscription is past due

A failed subscription charge is retried automatically. You do not need to do anything to trigger another attempt, and attempting to pay manually risks paying twice.

What happens to access depends on what is being paid for:

  • An autopay contract — session access is paused as soon as a charge fails, and comes back when a payment succeeds.
  • A subscription to a trainer or gym — it is marked past due while Stripe retries the card. Settings → My Subscription does not say so: while the subscription is past due, that screen reads "No Active Subscription" and shows no Manage Billing button until a payment succeeds.

To change the card:

  • If you are a member — the Manage Billing button on My Subscription does not open a billing portal for any member today (see the note above). Contact your trainer or gym: on your member page, under Billing, they can remove the card on file and add another.
  • If you are the account owner paying MyTrainerOS for your plan — billing is in a browser only: sign in at app.mytraineros.com and open Settings → Billing & Plan → Manage billing & invoices. The phone and tablet apps show the plan and have no billing button. If that button returns an error, contact us. The usual cause is that the account has no Stripe customer record, because it has never been through a plan checkout.

Members: who to contact

Your payments go to your trainer or gym, not to MyTrainerOS — we do not take a cut and we are not the merchant on your statement. For a refund, a disputed charge, or a question about what you were charged for, contact your trainer or gym directly. Contact us when the payment screen misbehaves.

Trainers and owners: a ledger entry labelled "No-Show Fee" that was not a no-show

A failed autopay payment is recorded with the wrong label. On the member's page, under Billing, the Account Ledger shows it as "No-Show Fee". Its note begins "Autopay payment failed", and the amount is what the member owes. Members do not see a ledger in the app.

Trainers and owners: payouts

Payouts are handled through Stripe, and a MyTrainerOS payments account has no Stripe dashboard to sign in to. If a payment succeeded but the payout has not arrived and you are the account owner, open Settings and look at the Stripe Connect row:

  • If it reads "Setup incomplete - action required", tap Complete Setup. The Payment Setup screen lists what Stripe still needs and shows whether payouts are enabled.
  • If it reads "Connected and ready to accept payments", tap Manage payments account. Any notice from Stripe is at the top of the Payments Account page. From a phone or tablet app that page opens in the device's browser, where you sign in to MyTrainerOS again.

A trainer working on someone else's account has no payments account: the row reads "Payments go to the account owner's Stripe account".

You are notified when a member's payment fails. Note that the member is not — so if it matters, reach out to them rather than assuming they have seen it.

My wearable isn't syncing

Applies to: Phone and tablet apps

Known limitation

MyTrainerOS reads health data through Apple Health (iOS) and Health Connect (Android) only. There is no direct device-brand login in the app. If your device does not write into one of those two, its data will not appear — and connecting it is a question for that device's own app, not for MyTrainerOS. Imported workout sessions and body-composition figures are not available yet, on any device.

Start here, because it is the step most people skip. MyTrainerOS does not connect to your watch or ring directly. It reads from your phone's health platform: Apple Health on iOS, Health Connect on Android. The chain is: your device → its own app → Apple Health or Health Connect → MyTrainerOS.

That means a break anywhere upstream looks identical to a MyTrainerOS problem. Check the chain in order:

  1. Does your device's own app show today's data? If not, the problem is between your device and its app. Nothing in MyTrainerOS can fix that.
  2. Does Apple Health / Health Connect show it? Open that app directly and look for today's sleep, resting heart rate, or steps. If it is missing there, your device's app is not writing to the platform — enable that in the device app's settings.
  3. Has MyTrainerOS been granted read permission? Open Settings → Wearable Devices (it is titled Health Data). Before you connect, the card says Not connected and shows a Connect button. On Android it then says Connected when all four data types are allowed, or Connected for 2 of 4, with the others marked Not allowed in Health Connect, when only some are. An iPhone never says Connected, because Apple does not tell an app whether reading was allowed: the card says Data received once readings have arrived, or No data received yet. To change what is allowed, use Apple Health or Health Connect itself, where each data type (resting heart rate, heart rate variability, sleep, steps) is allowed separately — so one can be on and another off.
  4. Pull to refresh on that screen, or tap Sync Now, to force a re-read.

If your device brand is not listed anywhere in the app, that is expected — there are no per-brand logins. Garmin, Fitbit, Whoop, Oura, Polar and Suunto devices reach us only by writing into Apple Health or Health Connect first, which is configured in that device's own app rather than in ours.

What we read, and what we deliberately do not

We read resting heart rate, heart rate variability, sleep duration and quality, and steps.

We do not show calorie burn from a wearable, and we are not going to. This is a deliberate product decision rather than a missing feature: wearable calorie estimates are unreliable enough that showing them would mislead your training and your nutrition targets. If you are looking for that number, you will not find it here.

Web browsers

Health data is read from the phone's health platform, so it is not available when you use MyTrainerOS in a browser. That is expected.

The app is slow or freezing

Applies to: Phone and tablet apps

  1. Force quit and reopen. Close the app completely — not just to the background — and start it again.
  2. Check for an update. Performance fixes ship regularly; an old build is a common cause.
  3. Free up storage. A phone close to full slows every app on it.
  4. Restart the phone. Unsatisfying, and it genuinely does resolve a class of problems that nothing else will.

If it is one particular screen rather than the whole app, say which screen when you file a ticket. "The app is slow" and "the member list takes 30 seconds when I have 400 members" are different problems with different fixes, and only the second one is actionable.

Still stuck?

If none of the above matches what you're seeing, send us a support request from the website: sign in at app.mytraineros.com in a browser and open Settings, then Support → Contact Support. If you cannot sign in, write to us from the contact page. Each user guide has a section on what to include so the first reply is a fix rather than a question.