Getting stuck in an endless “Authorization Revoked” or “Reconnect your tracker” loop inside MyFitnessPal happens when your wearable platform and MyFitnessPal hold mismatched security tokens. Simply hitting “Reconnect” inside the phone app rarely works for long—you have to revoke the old link from both platforms before creating a clean API handshake.
Quick Answer
Break the MyFitnessPal “Authorization Revoked” loop by disconnecting your wearable on both ends: unlink it inside MyFitnessPal (ideally on the web) and revoke MyFitnessPal’s access inside your Garmin, Fitbit, Oura, or Samsung account portal. Turn off VPNs or ad blockers, clear browser cookies, and reconnect once using matching account logins.
What Is Actually Happening?
When you connect Garmin Connect, Fitbit, Oura, WHOOP, or Samsung Health to MyFitnessPal, the two apps do not share your password. Instead, they trade temporary digital permission keys called OAuth tokens through an API (Application Programming Interface).
An “Authorization Revoked” loop happens when one side invalidates or forgets that token while the other side keeps trying to use it:
- One-sided disconnects: Removing the link inside the MyFitnessPal app often leaves an old ghost token sitting inside your wearable’s cloud account, which rejects the next connection attempt.
- Broken in-app browser redirects: When MyFitnessPal opens a mini browser window so you can sign into Garmin or Fitbit, strict ad blockers, VPNs, or stale cookies block the final redirect step that hands the fresh token back to MyFitnessPal.
- Duplicate accounts or login methods: Signing in once with an email address and later with “Continue with Apple/Google” creates a second empty profile or overwrites your active token, instantly revoking the previous session.
- Dual-bridge conflicts: Connecting a wearable directly via cloud API while also syncing the same data through Apple Health or Android Health Connect can cause permission collisions.
What to Do: Full Two-Sided API Reset
Follow this order carefully. Skipping the second unlink inside your wearable’s own account is the top reason the loop comes right back.
Step 1: Disconnect Inside MyFitnessPal
- Open a desktop or mobile web browser and sign in at myfitnesspal.com (web sessions handle OAuth cleanup more reliably than the cached mobile screen).
- Go to Apps (or in the mobile app, tap More > Apps & Devices).
- Find your connected wearable—such as Garmin Connect, Fitbit, Oura, or Samsung Health—and click Disconnect.
Step 2: Revoke Access Inside Your Wearable’s Portal
Open your wearable’s account settings separately and remove MyFitnessPal there too:
- Garmin: Log into connect.garmin.com > Profile / Account Settings > Account Information > Connected Apps (or Garmin Connect app > More > Settings > Connected Apps), find MyFitnessPal, and choose Disconnect / Revoke.
- Fitbit / Google: Open your Fitbit account settings (or Manage Data / Connected Apps) and revoke access for MyFitnessPal.
- Oura / WHOOP / Polar / Withings: Open the brand’s Integrations or Connected Apps menu in the app or web portal and unlink MyFitnessPal completely. (If only sleep metrics keep failing after reconnecting, see Why Your Oura Sleep Data isn’t Showing Up in MyFitnessPal.)
Step 3: Clean the Browser Handoff and Reconnect Once
- Temporarily turn off any VPN, iCloud Private Relay, or browser ad/tracking blocker on your phone or computer.
- Clear cached cookies for
myfitnesspal.comand your wearable’s login page (or open a fresh regular browser tab after clearing history—avoid private/incognito if your mobile app needs to bounce back cleanly). - In MyFitnessPal, go to Apps & Devices, select your wearable, tap Connect, and log into your wearable account carefully using the exact email tied to your watch or ring.
- Approve all requested permissions (do not leave exercise or calorie toggles unchecked).
What to Check If the Loop Returns
Audit Your Step Source and Health Hub Bridges
If the connection sticks briefly and drops again—or stops pushing calories and steps—check whether two bridges are fighting over the same metrics:
- In MyFitnessPal, go to More > Steps and select only one primary step source (for example, Garmin Connect or Apple Health, not multiple stacked trackers).
- If you sync via Apple Health on iOS, check Apple Health > Profile > Apps > MyFitnessPal and verify every Read and Write switch matches what you want shared—see Fixing “Read/Write” Errors in the Apple Health Sharing Menu.
- On Android, an interrupted Health Connect permission can mimic an expired API—follow How to Reset the “Health Connect” Permission Hub on Android 16 to rebuild a clean local link.
Watch for Circular Sync Loops
Connecting Strava, Garmin, Apple Health, and MyFitnessPal together in a triangle can trigger duplicate calorie adjustments or API conflicts; review The “Third-Party Loop”: Fixing Sync Errors Between Strava, Garmin, and Apple and Apple Health vs. Google Fit: Fixing the “Double Counting Steps” Bug if numbers start duplicating after you reconnect.
Reinstall MyFitnessPal to Flush Stuck Mobile Tokens
If the web portal stays connected yet the mobile app keeps flashing “Authorization Revoked,” sign out of the MyFitnessPal app, delete and reinstall the app, and sign back in using the exact same login method.
Bottom Line
Do not keep tapping “Reconnect” inside the MyFitnessPal app when an API token breaks. Unlink the integration on both MyFitnessPal and your wearable’s account portal, turn off VPNs or ad blockers during login, and re-authorize once from a clean session.