-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ensure users set buildNumber / buildDateTime when they try to OTA / sideload (if not just using tagged releases) #161
Comments
Just curious, how are you updating microg? I haven't encountered this issue. |
I updated it by installing an ota zip containing a newer µG version. This is on LineageOS 18.1 of course, forgot to mention it. What does the appcache do though? Because a workaround would be to simply wipe it on zip installation. |
I recommend bumping your |
This should do it: |
@zhaofengli is right. Every time I push a new build to my local device that isn't a tagged release I set I've had an idea to make this less likely to affect users: Set the type of |
It'd be nice if there was a build ID that was used to determine whether caches need to be cleared because we could just plug the drv hash into it to automatically get a new ID when the image is different (by Nix' definition). Though tbh, we could also just assume that every robotnix build is different to always cause wiping of caches and the like. The only optimisation we'd lose there would be in the case of installing the same image again but I don't think that's a particularly likely scenario. (And should you need to do that, you probably also want to wipe caches etc.) I think this is a serious issue we need to think more about, could this be re-opened? |
IIRC some apps (Google's I think), actually parses the BUILD_NUMBER as an integer--which was the reason GrapheneOS (and consequently robotnix) stopped including the periods in the YYYYMMDDhh tags and build numbers. Like, the buildDateTime, if we want to have build number be an integer, it should probably be monotonically increasing. |
With the most recent µG update, I got struck by this bug again but it has happened a lot in the past.
The
/system/data/appcache
becomes stale which causes µG to be displayed as the previous version in settings, have weird names (random strings used in µG), crash and generally not work well.Wiping the appcache makes µG work again without issue.
The text was updated successfully, but these errors were encountered: