-
-
Notifications
You must be signed in to change notification settings - Fork 793
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
bug: A "Disable auto updates" warning is unnecessary for non-root devices #2013
Comments
I remember seeing a lot of people asking for Change package name option because of playstore updater |
An app store could uninstall and install the update. The warning is necessary for non root users |
Sorry, I missed the existing issue. @Ushie But it doesn't solve the problem of patched apps showing up in the Play Store update list, so I doubt it makes sense. @oSumAtrIX But Play Store will never do that. In fact, the app store has never behaved like that. |
Play store is not the only app store. |
Does other stores have a privilege to uninstall the app automatically? |
I believe as long as they are the system app store, yes |
Oh, I forgot there are devices that has another app store in the rom. But I still doubt that there is an app store that will uninstall an app automatically just because it fails to update. |
We are working agnostic to any app and in terms of Android an auto updating app store could update the app even if the signature miss matches. Even Play Store can uninstall and install if you manually force it afaik |
As far as I know, Android won't allow it, even if it's a system app. Using the CorePatch source code as a reference, I looked at the source code of Android that compares signatures when updating an app, and I didn't find any flags or other stuff to avoid comparing signatures. InstallPackageHelper.preparePackageLI() -> SIgningDetails.checkCapability() -> hasCertificateInternal() Also, the Android docs article on third-party app stores states that apps with different signatures are incompatible and must be uninstalled in order to update:
No, if I attempt to manually update a re-signed app in the Play Store, Play Store will just show me a generic, unhelpful error message. ![]() Additionally, and importantly, the Play Store does not attempt to auto update re-signed apps. |
Other app stores could still auto update by reinstalling the app. The same can occur with PlayStore as stated in their ToS section "Updates" |
If the basis for the warning is that section of the ToS, then disabling auto update will have no effect.
|
Like I said multiple times already, Play Store is not the basis, thus neither it's ToS |
Bug description
When I tap the "Install" button after patching is completed, a warning will appear.
This dialog only appears on non-root devices.
On rooted devices, "Select install type" dialog appears instead.
However, this warning is unnecessary for non-root users.
Because patched apps have a different signature than original apps and will not be updated automatically.
Of course, manual updating is also impossible.
Therefore, this dialog should be removed.
Providing users an unnecessary instruction will confuse them.
Removing this dialog might be related to resolving #2012
Version of ReVanced Manager and version & name of app you are patching
ReVanced Manager v1.20.1 (stable)
Installation method
None
ReVanced Manager logs
Patch logs
No response
Acknowledgements
The text was updated successfully, but these errors were encountered: