Steps not being counted after the update

[skforty7]

NOOP version

8.4

Platform

iOS

OS version

IOS 26.5

WHOOP strap model

WHOOP 4.0

Where the data is coming from

Apple Health import

Test Centre profile

Steps

What happens

It says coming together

What you expected instead

Steps

Steps to reproduce

.

Strap log

{
  "app_version" : "8.4.0",
  "build" : {
    "channel" : "sideload",
    "signed" : false
  },
  "capture_check" : [
    {
      "count" : 33,
      "domain" : "steps",
      "status" : "ok",
      "tokens" : [
        "stepsRaw",
        "stepsCal"
      ]
    },
    {
      "count" : 67,
      "domain" : "universal",
      "status" : "ok",
      "tokens" : [
        "dayOwner ",
        "strapClock "
      ]
    }
  ],
  "os_version" : "Version 26.5 (Build 23F77)",
  "platform" : "iOS",
  "profile_started_at" : "2026-07-08T10:40:17Z",
  "questionnaire" : {

  },
  "redaction" : "v2",
  "schema" : 1,
  "source" : [
    "Live Bluetooth"
  ],
  "storage" : {
    "db_bytes" : 13115152,
    "raw_capture_bytes" : 0,
    "rows" : {
      "battery" : 38,
      "events" : 196,
      "gravity" : 28622,
      "hr" : 28725,
      "resp" : 28622,
      "rr" : 19223,
      "skinTemp" : 28622,
      "spo2" : 28622,
      "steps" : 0
    }
  },
  "strap_model" : "WHOOP 4.0",
  "test_profile" : "steps",
  "truncated" : false
}

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).

[ryanbr]

Thanks for the report and the export. Good news first: this isn't a bug from the update — I checked, and nothing in the steps, Apple Health, or import code changed between 8.3.x and 8.4.0. What you're seeing is a WHOOP 4.0 limitation plus a missing calibration input.

The key thing: a WHOOP 4.0 has no step counter over Bluetooth. So NOOP gets your steps from Apple Health — either shown directly, or as an estimate from the strap's motion that's calibrated against your phone's step count. Your export shows motion syncing fine (lots of HR/gravity rows) but steps: 0 and no Apple Health source — so no phone steps have been imported yet, and with nothing to calibrate against, the estimate is withheld. That "coming together"/Calibrating state is NOOP being honest that it can't count steps yet, rather than inventing a number.

To get steps going, either:

1. Run the Apple Health import and make sure Steps is allowed. In the iOS Health app → Sharing (or Profile → Apps) → NOOP → turn ON Steps, then run the import in NOOP. steps: 0 usually means the import wasn't run on this install, or the Steps permission specifically wasn't granted.
2. Or set it manually: Settings → Profile → Steps estimate → set the coefficient by hand. The estimate then works from strap motion without needing phone steps.

If you do the import with Steps enabled and it still reads 0, that's worth a closer look — could you grab a fresh debug log for it? In NOOP: More → Test Centre → turn on the Steps profile, use the app / run the import, then export the report and attach the .zip here (not a screenshot). That captures exactly where the step data stops, so I can pinpoint it if it's not just the permission.

[skforty7]

Thank you soo much.

…

On Wed, Jul 8, 2026 at 07:42 Fanboynz ***@***.***> wrote: *ryanbr* left a comment (ryanbr/noop#89) <#89 (comment)> Thanks for the report and the export. Good news first: this isn't a bug from the update — I checked, and nothing in the steps, Apple Health, or import code changed between 8.3.x and 8.4.0. What you're seeing is a WHOOP 4.0 limitation plus a missing calibration input. The key thing: *a WHOOP 4.0 has no step counter over Bluetooth.* So NOOP gets your steps from Apple Health — either shown directly, or as an *estimate* from the strap's motion that's calibrated against your phone's step count. Your export shows motion syncing fine (lots of HR/gravity rows) but steps: 0 and no Apple Health source — so *no phone steps have been imported yet*, and with nothing to calibrate against, the estimate is withheld. That "coming together"/Calibrating state is NOOP being honest that it can't count steps yet, rather than inventing a number. To get steps going, either: 1. *Run the Apple Health import and make sure Steps is allowed.* In the iOS *Health app → Sharing (or Profile → Apps) → NOOP → turn ON Steps*, then run the import in NOOP. steps: 0 usually means the import wasn't run on this install, or the Steps permission specifically wasn't granted. 2. *Or set it manually:* Settings → Profile → *Steps estimate* → set the coefficient by hand. The estimate then works from strap motion without needing phone steps. If you do the import with Steps enabled and it still reads 0, that's worth a closer look — could you grab a *fresh debug log* for it? In NOOP: *More → Test Centre → turn on the Steps profile*, use the app / run the import, then *export the report* and attach the .zip here (not a screenshot). That captures exactly where the step data stops, so I can pinpoint it if it's not just the permission. — Reply to this email directly, view it on GitHub <#89?email_source=notifications&email_token=CHQI3UCWP4MKNCVSQOWKNSL5DYXSNA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOJRGQ2DCMZVGIY2M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-4914413521>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/CHQI3UAAA7E24UHQZ3777IT5DYXSNAVCNFSNUABGKJSXA33TNF2G64TZHMYTENRVG44TSMZRHE5US43TOVSTWNBYGM3DONBZGEZDDILWAI> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/CHQI3UH3XCAQ6IZVCFRLO2L5DYXSNA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOJRGQ2DCMZVGIY2M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KUZTPN52GK4S7NFXXG> and Android <https://github.com/notifications/mobile/android/CHQI3UENZATOFPTZZRZE44T5DYXSNA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOJRGQ2DCMZVGIY2M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>. Download it today! You are receiving this because you authored the thread.Message ID: ***@***.***>

[Jenssaibe]

What about the old Apple Health export bug when the file is big, is it safe to try now ?

[skforty7]

I just uploaded the export to noop ,no problem .It says( need for days have=2 need=3)

…

On Wed, Jul 8, 2026 at 09:34 Jenssaibe ***@***.***> wrote: *Jenssaibe* left a comment (ryanbr/noop#89) <#89 (comment)> What about the old Apple Health export bug when the file is big, is it safe to try now ? — Reply to this email directly, view it on GitHub <#89?email_source=notifications&email_token=CHQI3UBIYMHGSG2RMKHPNF35DZEV7A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOJRGUZTGMZSGU42M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-4915333259>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/CHQI3UEO5Z5VBUZUYIZUHRT5DZEV7AVCNFSNUABGKJSXA33TNF2G64TZHMYTENRVG44TSMZRHE5US43TOVSTWNBYGM3DONBZGEZDDILWAI> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/CHQI3UBIATO64JPIRLMZ6QT5DZEV7A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOJRGUZTGMZSGU42M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KUZTPN52GK4S7NFXXG> and Android <https://github.com/notifications/mobile/android/CHQI3UG4TTTLOSMUQEH2M4D5DZEV7A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOJRGUZTGMZSGU42M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>. Download it today! You are receiving this because you authored the thread.Message ID: ***@***.***>

[Jenssaibe]

How big is your export ?

[skforty7]

Around 12 mb.

…

On Wed, Jul 8, 2026 at 12:12 Jenssaibe ***@***.***> wrote: *Jenssaibe* left a comment (ryanbr/noop#89) <#89 (comment)> How big is your export ? — Reply to this email directly, view it on GitHub <#89?email_source=notifications&email_token=CHQI3UBE4XHZLGECMPINZQD5DZXILA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOJRGY4DEOJSHA2KM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-4916829284>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/CHQI3UATLQUCKLSMNKLPN6T5DZXILAVCNFSNUABGKJSXA33TNF2G64TZHMYTENRVG44TSMZRHE5US43TOVSTWNBYGM3DONBZGEZDDILWAI> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/CHQI3UFLH53ZHF4BJVUU6V35DZXILA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOJRGY4DEOJSHA2KM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KUZTPN52GK4S7NFXXG> and Android <https://github.com/notifications/mobile/android/CHQI3UBXODFSARYOAVPRQT35DZXILA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOJRGY4DEOJSHA2KM4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>. Download it today! You are receiving this because you authored the thread.Message ID: ***@***.***>