You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
0.11.3 - Possibility: rebuilding export/import system from the ground up (at least for edge files) #606
I recently hit the 30 day mark and with the arrival of v0.11.3 I decided to update the app, run an export, uninstall the app, reinstall, and start from zero. A few days in though I was missing the recovery and so brought in the import https://drive.google.com/file/d/1XEmxLvccHxJ9cn0pGeT6zyqH1Vj6RKVH/view?usp=drivesdk
which failed to load with this error:
I was able to rearrange the structure and get the data imported by throwing it into Claude but it didn't populate the last 30 days:
After meandering through the data for a while, I asked Claude how it'd rebuild the export/import system to both speed up imports and ensure better restoration of edge exports (I'm assuming these can be chucked into another Claude/AI instance as instructions for a future pr if it's decided the export/import system should be rebuilt)
Steps to reproduce
Wear for a while from square one (no import)
Export your data
Uninstall the app
Reinstall the app
Attempt to import your export
App version
0.11.3
Platform
Android (APK)
Phone model and OS version
Moto G power 2022 - Android version: 12 S3RQS32.20-42-10-9-12
Which band?
WHOOP 4.0
Screenshots
No response
Quick checks
The official WHOOP app is not also connected to this band
The refusal in your first screenshot ("not a NOOP backup — it has no hrSample table") is fixed by #701, merged and due in the next release after 0.11.3. The app recognised its own backup by file name only, so a backup that came back from Drive under a different name went to the NOOP importer. It now checks the file's contents. With that, the original export should import directly, with no restructuring. The missing last 30 days most likely came from the rearranged file. A full rebuild of export/import is a maintainer call; once the release is out, it would help to know whether the original file now restores everything.
the "not a noop backup" refusal was because the app only recognised its own backup by file name, and drive renamed yours. 0.12.2 checks the file contents instead, so your original export should import directly without restructuring. could you try it on 0.12.2 and tell me whether the last 30 days come back? if not, a report from the app after the import would help me see where they get dropped.
Activity
Recognise the app's own backup by content, not only by name (#606)
kurexw commentedon Nov 15, 2026
The refusal in your first screenshot ("not a NOOP backup — it has no hrSample table") is fixed by #701, merged and due in the next release after 0.11.3. The app recognised its own backup by file name only, so a backup that came back from Drive under a different name went to the NOOP importer. It now checks the file's contents. With that, the original export should import directly, with no restructuring. The missing last 30 days most likely came from the rearranged file. A full rebuild of export/import is a maintainer call; once the release is out, it would help to know whether the original file now restores everything.
abdulsaheel commentedon Nov 17, 2026
the "not a noop backup" refusal was because the app only recognised its own backup by file name, and drive renamed yours. 0.12.2 checks the file contents instead, so your original export should import directly without restructuring. could you try it on 0.12.2 and tell me whether the last 30 days come back? if not, a report from the app after the import would help me see where they get dropped.