Fix: steps not syncing
Direct answer
Confirm Apple Health access, allow a fresh step sample, and then reopen MoveFirst. Diagnose one layer at a time and retest after each change, so the result identifies a cause rather than a lucky reset. Write down the intended outcome before making the rule stricter.
The App Store link is being confirmed. See how MoveFirst works below.
- Symptom
- Steps not syncing
- First evidence
- 20 min · 7 days
- Escalation record
- Checked 2026-08-15
A practical setup
For steps not syncing, capture the iOS version, MoveFirst version, permission state, selected-app count, and whether today is locked or already open before changing settings. Start with the smallest app group or setting that still tests the idea clearly.
Worked example
Run one short reproduction, make one change, lock the iPhone briefly, and repeat the same test instead of toggling several controls together. Use the same setup on calm and tired days before drawing a conclusion.
Separate a missing Health sample from a stale MoveFirst display. In Apple Health, confirm that a recent step value exists and note its timestamp and contributing device before opening MoveFirst. Verify only the step permission used by this route; leave camera, Screen Time, and app selection unchanged. Walk long enough for one fresh sample, wait for Health to show it, then reopen MoveFirst once and compare the two timestamps rather than estimating from memory. Remember that the target is a fixed 8,000 steps, so a partial total opens nothing. Record the iPhone model, iOS version, MoveFirst version, Health value, displayed MoveFirst value, and the exact observation time. If Health itself has not updated, let its sources settle; if Health is current but MoveFirst remains stale, preserve that paired evidence for support and use a camera session or a named place meanwhile.
How to measure the experiment
Use up to 5 reproducible checks across permission, selection, movement input, and today’s open-or-locked state; stop when one layer changes the result. A difficult day is useful evidence, but it should not decide the whole experiment by itself.
Before you switch it on
Good troubleshooting starts with a reproducible case and ends with the smallest confirmed fix.
- Record the exact expected and observed behavior.
- Verify the relevant Apple permission first.
- Retest one selected app or one movement input.
- Keep versions and results ready if support is needed.
When to adjust the rule
Escalate with the recorded facts when the same test still fails after permission, selection, and a single relaunch are verified. Shorten the access window before raising the physical effort if sessions are simply running too long.
Continue with a related guide
The App Store link is being confirmed. See how MoveFirst works below.
The App Store link is being confirmed. See how MoveFirst works below.
The App Store link is being confirmed. See how MoveFirst works below.