this post was submitted on 06 Mar 2024
900 points (100.0% liked)

196

17554 readers
752 users here now

Be sure to follow the rule before you head out.


Rule: You must post before you leave.



Other rules

Behavior rules:

Posting rules:

NSFW: NSFW content is permitted but it must be tagged and have content warnings. Anything that doesn't adhere to this will be removed. Content warnings should be added like: [penis], [explicit description of sex]. Non-sexualized breasts of any gender are not considered inappropriate and therefore do not need to be blurred/tagged.

If you have any questions, feel free to contact us on our matrix channel or email.

Other 196's:

founded 2 years ago
MODERATORS
 

inspired by this post. the app was €300.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 5 points 1 year ago (1 children)

You don't need to implement support for rollbacks to handle those "emergency" rollbacks. You could just push a "new" version that's actually the last known good version, and the phone would happily install it.

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago) (1 children)

You can only do this if you have the signing keys. If the store wants to do this for users (say, if the developer is incapacitated somehow) they can't.

Edit: I'm actually not 100% sure if the signing keys are required for changing just the version number, but I assume so

[–] [email protected] 3 points 1 year ago

That sounds about right for Google play. That said, the point still stands. If Google wanted to implement such a feature, it could probably be done by onky patching things on their store backend. I'm sure it wouldn't be a trivial change, but still it wouldn't need to touch the OS itself. Probably. As far as the phone is concerned, it would still be disallowing rollbacks as usual.