Repository navigation
馃洃 Heads up: patched apps need聽a one-time reinstall #181
fahim-ahmed05
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I聽changed the signing key for everything built here. From build
260211聽(beta) and260212(stable) onward, every APK and module zip is signed with my own key instead of the one that came with the project template I forked this from.Why I did it: that old key was public. The private half ships inside the template, so anyone who forked the same project could have handed you a modified APK that installed over my builds like a normal update, and your phone would have accepted it. That's fixed now.
What you need to do, one time: uninstall the patched app, then install the latest build from the release page. Android will not let an app signed with聽a different key update over the old one, so you'll see "app not installed" or聽a signature conflict if you try. Log back in afterwards.
One thing to check before you uninstall: anything stored inside the app data goes away with it. For Discord that means your Revenge plugins, themes and settings. Export or note them down first.
If you use the KernelSU or Magisk modules, remove the old module and flash the new zip. Module updates hit the same signature wall.
If you want to check the key yourself instead of taking my word for it, the signer is CN=nullcpy rvb signing key and its SHA-256 is
f7ebda59聽1f43fb2c 3b9258d9 2b791f8c 46b25d4b 42293e5c聽7f27f3cb e1bbbe5a. The old one was CN=ReVanced, which should tell you everything about where it came from.Sorry for the hassle of reinstalling. It's a one-time thing, and updates work normally after this for the next 30 years. 馃檪
Closed #139
All reactions