Troubleshooting Guide
MyFitnessPal Not Reading Apple Health Steps
Fix myfitnesspal not reading apple health steps on iPhone with clear, testable steps. Diagnose permissions, sync delays, and data source issues in minutes.
Start Fix Now
MyFitnessPal Not Reading Apple Health Steps usually happens when one app can write steps but the other app cannot read them yet. Reconnecting permissions and forcing a small sync test usually resolves it in 10 to 20 minutes.
Do the first three fixes now before reading diagnostics. In most cases, one of them solves the issue quickly.
Fix 1
Disconnect Apple Health inside MyFitnessPal, then reconnect and re-allow step read access.
Verify in 2-4 minutes: Connection status is active and step permissions are still enabled.
Go to Step 1Fix 2
Open Health Sharing and confirm the integration app has step permissions.
Verify in 1-3 minutes: Both read and write toggles are correct for the app role.
Go to Step 2Fix 3
Disconnect the integration and reconnect once.
Verify in 2-4 minutes: Reconnection completes and no permissions are missing.
Go to Step 3Before you start
Use this baseline so you can verify each fix quickly:
- Note your current step count in Health.
- Walk exactly 100 steps at normal pace.
- Recheck after 2 to 5 minutes.
What a successful fix looks like
- New steps appear without forcing repeated app refreshes.
- Widget and app values stay close after a short sync delay.
- Source order and permissions remain saved after restart.
Issue-specific note
MyFitnessPal is connected but step import stays unchanged.
Step-by-step fix flow
0/8 completeRun these in order. Each step has exact taps, wait time, success check, and fallback if it fails.
1. Disconnect Apple Health inside MyFitnessPal, then reconnect and re-allow step read access.
Where to tap: Integration app settings > Connected Apps or Health permissions.
Wait time: 2-4 minutes
Pass/fail check: Connection status is active and step permissions are still enabled.
Expected result: This removes the most likely blocker for this issue.
If this failed, go to Step 22. Open Health Sharing and confirm the integration app has step permissions.
Where to tap: Health app > Sharing > Apps > your integration app.
Wait time: 1-3 minutes
Pass/fail check: Both read and write toggles are correct for the app role.
Expected result: App now has full required access.
If this failed, go to Step 33. Disconnect the integration and reconnect once.
Where to tap: Integration app settings > connected apps/permissions.
Wait time: 2-4 minutes
Pass/fail check: Reconnection completes and no permissions are missing.
Expected result: Sync token is refreshed.
If this failed, go to Step 44. Open source app and destination app back to back.
Where to tap: Open both the source app and destination app.
Wait time: 2-5 minutes
Pass/fail check: Each app shows recent sync time or updated count.
Expected result: Data starts moving between apps.
If this failed, go to Step 55. Keep iPhone unlocked on Wi-Fi for 3-5 minutes.
Where to tap: Settings app section related to this step.
Wait time: 3-5 minutes
Pass/fail check: Do not force close either app during this window.
Expected result: Delayed sync jobs complete.
If this failed, go to Step 66. Perform a 100-step walk and trigger manual sync if available.
Where to tap: Health app > Steps view during the test.
Wait time: 3-5 minutes
Pass/fail check: Check source app first, then destination app.
Expected result: New steps arrive in destination app.
If this failed, go to Step 77. Check date/time and timezone are automatic.
Where to tap: Settings > General > Date & Time.
Wait time: 2-5 minutes
Pass/fail check: Automatic settings are enabled in Date & Time.
Expected result: No date-boundary sync mismatch remains.
If this failed, go to Step 88. Sign out and sign back in to the integration app only if sync is still broken.
Where to tap: Account settings in the integration app.
Wait time: 3-5 minutes
Pass/fail check: Account reconnect finishes and permissions stay enabled.
Expected result: Stuck sync state clears.
Note: Use this only after earlier steps fail to avoid unnecessary resets.
If this failed, contact Apple Support
Issue fixed?
Let us know if this guide solved it. This helps us improve the steps.
Symptoms (Diagnostic)
Use this only if your issue still is not fixed after the first steps.
ShowHide
Symptoms (Diagnostic)
Use this only if your issue still is not fixed after the first steps.
| Symptom | What you see | Likely cause confidence |
|---|---|---|
| MyFitnessPal Not Reading Apple Health Steps | MyFitnessPal is connected but step import stays unchanged. | High |
| Delayed or stale updates | Counts stay the same for several minutes even after walking. | Medium |
| Cross-app mismatch | Health, widget, or connected apps do not show the same total. | High |
Root Causes (Diagnostic)
If steps are still missing, verify these causes in 30 seconds each.
ShowHide
Root Causes (Diagnostic)
If steps are still missing, verify these causes in 30 seconds each.
| Cause | Why it happens | Verify in 30 seconds |
|---|---|---|
| Token handshake is stale after an app update or account relogin. | MyFitnessPal is connected but step import stays unchanged. | Connection status is active and step permissions are still enabled. |
| Read/write permissions are not aligned | One app can write steps, but the destination app cannot read them. | Check Health Sharing permissions for the integration app. |
| Sync token is stale | App updates or relogins can break an existing sync handshake. | Disconnect and reconnect the integration once. |
Related fixes
If your current issue is close to one of these, open it next.
iOS notes
Across recent iOS versions, most step issues come from permissions, source order, or refresh delays, not sensor hardware failure.
ShowHide
iOS notes
Across recent iOS versions, most step issues come from permissions, source order, or refresh delays, not sensor hardware failure.
| Scenario | What to expect | Action |
|---|---|---|
| Fresh app install | Initial sync may need manual app open on both ends. | Open both apps and wait 3-5 minutes. |
| Background-only expectation | Some integrations sync less often in background. | Trigger one manual sync after a short walk. |
| Timezone changes | Day boundary mismatches can delay day totals. | Keep Date & Time automatic. |
When to contact Apple Support
Contact Apple Support if Health receives data but integration apps never sync even after reconnecting permissions.
- Integration app shows no update after reconnect, manual sync, and a fresh walk test.
- You completed every checklist step and repeated the 100-step test twice.
- The issue affects multiple days or causes major data loss.
FAQ
Why is myfitnesspal not reading apple health steps happening?
MyFitnessPal Not Reading Apple Health Steps is most often caused by one blocked setting, one stale sync connection, or one source-priority conflict. The checklist above isolates each cause in a testable order.
How long should I wait before checking the count again?
After each change, wait 2 to 5 minutes and then do a short 100-step walk test. Rechecking too quickly can look like a failure when data is still syncing.
What should I do if this still does not work?
Finish all checklist steps once, collect screenshots with timestamps, and use the Apple Support trigger section on this page to escalate with evidence.