Releases marked "pre-release" on github seem to be getting automatically pushed to the Play Store & auto-installed on devices

[gabrielgrant]

I have not opted in to an update at all, nevermind manually installing a pre-release or beta, but my device now reports running v0.14.0 (rust) and the Play Store description seems to imply the latest deployed version there is 0.14.0beta2 (with the latest Updated on date listed as 20 Aug 2026)

I'm not sure if this is intentional, but seems like these releases should probably be held from auto-updating people who haven't opted in, at least until they are considered fully stable

FWIW, it seems my multiple years of AW history are no longer available, and the disappearance seems to correspond with this latest release having been auto-installed

I see there are some open issues (eg #149 ) about existing databases not being migrated, so I'm hoping my old data is not permanently lost (though it's unclear how to actually access it), but even if that is recoverable, it disappearing from the UI seems like a critical bug that should absolutely be (or have been) addressed before a widespread public auto-updated release like this.

[ErikBjare]

Thank you for reporting,

It was intentional and a manually triggered promotion to production track from the internal beta track after having been tested and considered stable enough to release (the previous version was getting truly embarrassing). The update was required by Play Store to clear a bunch of long-standing requests whose deadlines approaching meant the app would not remain in the store, so would otherwise have been uninstallable around this time.

We are monitoring Play Store-reported vitals for regressions on #176 / #185 / #189 (they are quite delayed), and noting any UX issues this upgrade may cause (thanks for reporting!)

No data can be truly lost by the upgrade afaik. If you have truly lost data as a consequence of this upgrade, please detail what that looks like. What I suspect is that for you, the "Raw data"/buckets view still has the old aw-watcher-android-test bucket (old bucket, it was always poorly named), which is no longer queried by the "Activity" view in favor of the (correct) aw-watcher-android bucket. If this is not it, then. I apologize the migration wasn't smoother, I aim to clean this up in an update (merging old aw-watcher-android-test buckets into new aw-watcher-android bucket as long as it seems safe/non-overlapping).

Another UX quirk I noticed the other day on a friends device is that if you have set "Landing Page" in Settings to "Activity (unknown)" (the previous only option) then that would too result in the Activity view seemingly showing no activity. A simple fix is to simply re-set the setting from the available options in the drop-down.

Thanks for reporting! You are the first person who reported an issue for this release!

[TimeToBuildBob]

CI-side leftover from this thread is now #245: the Build workflow fail-closes if a pre-release tag would publish to the production Play track, and the job summary records the resolved SUPPLY_TRACK.

That does not change Play Console promotions. Erik's note stands — v0.14.0b2 reaching production devices was a manual promotion from internal, not a CI mapping bug. #245 only stops that class of failure from happening via the tag→fastlane path.

Bucket-migration / history-gap remains #244 (and #149). Do not treat #245 as closing this issue.