Joe Maring / Android Authority

Testing Google’s latest software always involve balancing some trade-offs: Sure, you get first crack at trying out some of the latest features, but that also means tolerating a few bugs along the way. And while that can be a lot of fun, testers might be feeling understandably excited when a new stable release finally comes out — like Android 17 earlier week — and they can easily opt out of testing and all the uncertainty that comes with it. At least, that’s how it’s supposed to work, but some glitches have been making it more difficult than it should be for some testers to make that transition.

While Google makes it pretty easy to get started testing an Android Beta, leaving the program can be a little tricky — that is, if you want to avoid a full device data wipe, forcing you to restore your app content from a backup. But there’s always still a light at the end of the tunnel, and you can opt out when the stable release is ready, moving directly to that update, and not lose your data in the process.

The problem is, while some testers on Android 17 Beta 4 found themselves able to move to this week’s stable release without issue, those on Android 17 Beta 4.1 have been posting to Reddit about their inability to do the same. Glitches like these aren’t exactly uncommon, and we’re usually looking at a mismatch between patch levels on affected devices, making the old software appear more up-to-date than the new one you want to replace it with.