OAuth Troubleshooting
Diagnose and fix integration issues with your fitness trackers
OAuth Testing & Diagnostics
This tool tests your fitness tracker connections and OAuth permissions to identify issues with data access, friend discovery, and social features.
Sign in to run OAuth tests
Common Issues
401 Unauthorized Errors
Token expired or insufficient permissions. Try reconnecting your integration.
Social Features Not Working
Strava requires profile:read_all scope for friend discovery. Reconnect with social permissions.
Data Not Syncing
Check activity:read_all permissions and verify your activities are public.
Quick Fixes
Reconnect Integration
Go to Settings → Integrations → Disconnect → Reconnect
Clear Browser Data
Clear cookies and cache, then try OAuth flow again
Check Provider Settings
Verify privacy settings on Strava/Fitbit allow third-party access
Detailed OAuth Troubleshooting Guide
Understanding OAuth Flow
- You click "Connect Strava" in Grow-Fit Club
- You're redirected to Strava's authorization page
- Strava shows requested permissions (scopes)
- You authorize and get redirected back with a code
- Grow-Fit Club exchanges the code for access tokens
- Tokens are used to access your fitness data
OAuth Scope Meanings
Strava Scopes
read - Basic profile accessactivity:read_all - All activity dataprofile:read_all - Social/follower dataFitbit Scopes
activity - Steps, distance, caloriesheartrate - Heart rate dataprofile - Profile and friendsAdvanced Debugging
If basic troubleshooting doesn't work, check these technical details:
- • Browser developer tools console for JavaScript errors
- • Network tab to inspect OAuth redirect URLs
- • Check if popup blockers are preventing OAuth windows
- • Verify system clock is accurate (affects token validation)
- • Test in incognito mode to rule out extension conflicts