Strava Privacy Settings That Break Sync: Common Pitfalls and Fixes
5 min read
Strava activities not syncing? Reauthorize connected apps, check activity visibility and privacy zones, test route export, and use a clean manual import if needed.
On this page
Photo by john crozier on Unsplash.
If Strava activities stop syncing, start by reauthorizing the device or app connection, then check visibility and privacy settings.
Most sync failures are not a sign that your watch, head unit, or phone has failed. The common blockers are account mismatch, stale app permission, activity visibility, route privacy, or a file that needs manual import.
Photo by Robin Vintevogel on Unsplash.
Strava sits between your device account and the training tools that read the ride later. When that chain breaks, the file may still reach Strava while linked apps see nothing.
The usual cause is a closed gate, not broken hardware. Check app-to-app permissions before you reset devices or rebuild your whole setup.
If you use N+One after Strava, confirm the activity made it through the import path and that key ride fields are present. This guide on how N+One imports Strava rides shows what to verify before changing training data.
Check app-to-app permissions before hardware troubleshooting.
Confirm the same Strava account is linked everywhere.
Look for private activity or route settings.
Treat revoked permissions as a likely blocker.
Start with the connection, then check privacy only if sync still fails.
In N+One terms: the training system around your device still works — a privacy gate is stopping the data flow.
Activity Visibility controls who can see a ride, while segment and map privacy can hide parts of it. Some linked tools need enough shared detail to match the file, route, or segment data.
A fully private activity may upload cleanly from your device but fail to flow outward as expected. If the ride is missing downstream, test a less strict setting on one recent activity.
For Garmin-linked workflows, compare Strava privacy with your device account settings before blaming the head unit. The same logic applies when Garmin activity privacy affects sync across linked training apps.
Set one test activity to followers or everyone.
Retry sync after the visibility change.
Keep start and end hidden if needed.
Avoid making the whole test ride private.
Use the least open setting that lets the activity move.
In N+One terms: open the gate briefly to confirm it’s the privacy setting, then reapply the minimal privacy you need.
One clear next move: reauthorize the external connection (Garmin/Apple Health/Fitbit) and trigger a fresh sync.
Connected apps rely on permission grants between services. If a grant is revoked, stale, or tied to the wrong account, automatic sync can stop without changing the original ride file.
A common sign is simple: manual upload still works, but auto-sync fails. Another sign is a partner dashboard showing disconnected, expired, or missing access.
Revoke the connection first, then sign in again from the partner app so both sides rebuild the handshake. If your ride appears twice after repair, use a cleanup workflow for one ride from multiple sources.
Open Strava Settings, then My Apps.
Revoke the affected partner app.
Sign back in through the partner service.
Confirm connected status on both sides.
Reauthorization is the cleanest first move when uploads exist but sync does not.
In N+One terms: reestablish the handshake between services rather than replacing the device.
One tactical email with training ideas and product updates. No spam — unsubscribe anytime.
Keep reading
- Backdating a Manual Ride in N+One: Preserving Your Training Stress History — Learn how to backdate a manual ride in N+One, set the correct past date and time, add duration and intensity, and verify your training history.
- Combining HRV Sources: Reconciling WHOOP, Oura, and Apple Watch for Cycling Decisions — WHOOP, Oura, and Apple Watch HRV can disagree. Learn how to choose one primary source, normalize baselines, and make clearer cycling training decisio...
- Fixing WHOOP sync data gaps — Troubleshoot WHOOP sync data gaps: quick checks, reconnect steps, and when to escalate so recovery values update reliably.
Routes add another layer because the linked app may need coordinates, not just a ride title. Private routes, hidden map data, or blocked export files can break import while the activity remains visible.
If a route will not move, export the file and test whether another tool can read it. A readable file points back to app permission or visibility, while an unreadable file points to export trouble.
Use GPX or TCX when route shape matters, and FIT when you need richer device data. If power values look off after re-sync, compare sources with matching Strava and Garmin power.
Make one route public or shared for testing.
Export GPX or TCX from Strava.
Import the file manually into the partner app.
Check that coordinates are present.
In N+One terms: confirm the route file can be read before troubleshooting sync logic.
Run the checks in order so you do not chase the wrong fault. First confirm the activity exists in Strava, then test visibility, then rebuild the partner connection.
If the file reaches Strava but not your training app, reauthorize the partner app now. If that fails, make one test activity visible to followers, retry sync, then return to your normal privacy setting.
When numbers still look wrong after the activity lands, force a fresh pull instead of editing the ride by hand. This is where forcing a clean re-sync can protect the training record.
Confirm the activity appears in Strava.
Set one test ride to followers.
Reauthorize the partner app.
Manual import the file if sync still fails.
Step 1 — Confirm upload to Strava: Open Strava on web or app and ensure the activity file from your device is visible in your feed. If the activity is not present, re-upload the file manually from the device export.
Step 2 — Test visibility: Change that activity’s visibility to followers, or everyone briefly. Wait a short time and check the partner app. If it appears, privacy was the blocker.
Step 3 — Reauthorize partner app: Go to Strava Settings, then My Apps. Revoke the partner app, then re-authorize it by signing into the partner service and granting permissions. Confirm the partner app shows as connected.
Step 4 — Verify route and export settings: If routes or segments are failing, make the route public or export the GPX or TCX from Strava. Import it into the partner app manually to confirm the file is readable.
Step 5 — Final test and reset minimal privacy: Upload a second test activity and set the least permissive privacy that still allows sync. For many riders, that means hiding start and end, not the whole activity.
If Strava activities stop syncing, start by reauthorizing the device or app connection, then check that the same account, activity visibility, and route privacy settings still allow data to move.
Yes. A ride can reach Strava from your device while remaining hidden from some linked services. Test one recent activity with less strict visibility, then restore the narrowest privacy setting that still syncs.
No. Start with reauthorization because it is cleaner and faster. Reinstall only after you confirm the activity exists in Strava, privacy is not blocking it, and the partner app still will not connect.
Sign out of both services and confirm the account email or profile on each side. A mismatched account can make sync look broken even when both apps are working.
Contact Strava Support after you test visibility, reauthorize the partner app, update apps, and try manual export or import. Include timestamps, file type, device source, and screenshots of connection status.