Repository navigation
The Steps Tracking #1491
Description
NOOP version
10.1.1
Platform
iOS
OS version
iOS 18.7
WHOOP strap model
WHOOP 4.0
Where the data is coming from
Live Bluetooth (strap connected)
Test Centre profile
Steps
What happens
Tracking steps does not work. I imported some data from the Whoop application, but the application still does not recognize the steps
What you expected instead
The app recognizes the number of steps
Steps to reproduce
Is there any step I can take to solve this problem ?
Strap log
Before you submit
- I attached my exported NOOP .zip (not a screenshot of the Live screen). If my bug is a clearly reproducible UI issue I described exactly how to see it instead.
- I attached or pasted a strap log above — or my bug is a clearly reproducible UI issue that doesn't need one (e.g. a typo, a button that does nothing) and I've described exactly how to see it.
- I checked the Troubleshooting guide — especially "history syncs but no data" (most often the strap isn't banking history to flash; charge it to 100% and reconnect).
- I checked the FAQ and — if I'm on a WHOOP 5.0 / MG — the 5.0/MG status page, and this isn't an already-known limit (e.g. SpO₂, or recovery/sleep on the 5/MG).
- I've left out anything personal (strap serial, account email, raw export).
Activity
Show the steps-calibration prompt to the users it was written for (#1491
Show the steps-calibration prompt to the users it was written for (#1491
Give the Android Steps tile the caption it has been computing all alo…
Give the Android Steps tile the caption it has been computing all alo…
ryanbr commentedon Aug 21, 2026
Explaining what's happening, because two of the three things here you can act on today.
A WHOOP 4.0 sends no step count. NOOP estimates steps from the strap's motion and calibrates that
against a step count your phone measured for the same day. Until it has that reference it withholds the
estimate rather than guessing — which is why the tile is blank. Your WHOOP app import can't help: it
carries no phone step count, which is the one input the calibration needs.
Two things that will:
iPhone's steps hourly and does a one-time 90-day backfill, so the calibration reference arrives
retroactively rather than after days of wear. Make sure NOOP has Health access when it asks.
works immediately.
The third thing was our bug, now fixed (#1512): the tile was supposed to say "Connect your phone's step
count to estimate steps" and offer a shortcut to that sheet. It never appeared, because the check for
"should we explain this?" required calibration to have already started — so the people who had not started
were the only ones who never saw it. You were the exact case it was written for.
Android had the same dead end by a different route; that's fixed too (#1514).
Thanks for reporting it. "I imported data and it still doesn't recognise steps" is what made the gap
obvious — an import is a perfectly reasonable thing to expect to work, and nothing on screen said why it
didn't.
Check what the user set, not only what the engine later wrote (#1515)
Stop telling a calibrated user they need 0 more days, on both platfor…
A 5/MG never sees the steps-calibration prompt, coefficient or not (#…