Skip to content

0.11.3 - Possibility: rebuilding export/import system from the ground up (at least for edge files) #606

Open

Description

@cb0806151

What happened?

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:

Image

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:

Image

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)

Image Image Image Image

Steps to reproduce

  1. Wear for a while from square one (no import)
  2. Export your data
  3. Uninstall the app
  4. Reinstall the app
  5. 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
  • I've searched existing issues for this

Activity

  1. kurexw commented on Nov 15, 2026

    @kurexw
    Contributor

    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.

  2. abdulsaheel commented on Nov 17, 2026

    @abdulsaheel
    Collaborator

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions