Closed pmsobrado closed 11 months ago
Play Protect triggers for "Unknown" apps, which the Play Protect doesn't recognize the "signature" of.
The way ReVanced works is everything is done on your device, it decompiles the provided APK, applies changes, compiles it, signs it, and installs it
When ReVanced Manager signs an app, it needs to generate a new Keystore, what's a keystore? it is basically the key to signing apps with your developer "signature", and considering the Keystore is generated by ReVanced Manager, the signature will be unique.
The reason you didn't see this on older releases of ReVanced Manager is either Play Protect was acting silly, or you've already gone through the Play Protect warning once and forgotten about it (which means it learned about the signature)
As to why you don't see this happen to other APKs, it's because these APKs aren't compiled on your device, they've already been installed, tested, and all by the dev and other people who installed it before you. You'll see the same behavior when using other projects that generate the Keystore locally, such as Aliucord, Vendetta, LuckyPatcher(?)... etc
Thanks for the explanations. I have a question though:
The reason you didn't see this on older releases of ReVanced Manager is either Play Protect was acting silly,
or you've already gone through the Play Protect warning once and forgotten about it (which means it learned
about the signature)
Why if I try to install Revanced again, the Play Protect prompt appears as the first time? Shouldn't it already know the signature from the previous installation? Or maybe Play Protect only stops complaining when the signature has been "used" a few times?
I'm not sure what the exact process is, there used to be a button that sends information about the application to Play Protect to scan and determine that it's safe, but I don't see that button anymore
To sum up, for X reason the older build has a key that was "accepted" by Play Protect at some point xD
So does that imply prebuilt patch will no longer work? I tried install the yt patched apk but it crash each time I open it:
05-13 23:48:19.108 E/AndroidRuntime(19562): FATAL EXCEPTION: main
05-13 23:48:19.108 E/AndroidRuntime(19562): Process: app.revanced.android.apps.youtube.music, PID: 19562
05-13 23:48:19.108 E/AndroidRuntime(19562): java.lang.SecurityException: PackageVerificationRslt: not allowed: pkg=app.revanced.android.apps.youtube.music, sha256=[818684e946ab7c1c298187f52f34455e15b386a07fa990d6c22268fab586ad60], atk=true, ver=241518018.true
05-13 23:48:19.108 E/AndroidRuntime(19562): at android.os.Parcel.createException(Parcel.java:2072)
05-13 23:48:19.108 E/AndroidRuntime(19562): at android.os.Parcel.readException(Parcel.java:2040)
05-13 23:48:19.108 E/AndroidRuntime(19562): at android.os.Parcel.readException(Parcel.java:1988)
05-13 23:48:19.108 E/AndroidRuntime(19562): at gns.a(SourceFile:14)
05-13 23:48:19.108 E/AndroidRuntime(19562): at gmr.a(SourceFile:220)
05-13 23:48:19.108 E/AndroidRuntime(19562): at gis.a(SourceFile:29)
05-13 23:48:19.108 E/AndroidRuntime(19562): at giw.run(SourceFile:10)
05-13 23:48:19.108 E/AndroidRuntime(19562): at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:462)
05-13 23:48:19.108 E/AndroidRuntime(19562): at java.util.concurrent.FutureTask.run(FutureTask.java:266)
05-13 23:48:19.108 E/AndroidRuntime(19562): at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
05-13 23:48:19.108 E/AndroidRuntime(19562): at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
05-13 23:48:19.108 E/AndroidRuntime(19562): at hdm.run(SourceFile:6)
05-13 23:48:19.108 E/AndroidRuntime(19562): at java.lang.Thread.run(Thread.java:919)
05-13 23:48:19.109 E/mvo (19562): APP CRASHED!
05-13 23:48:19.109 E/mvo (19562): java.lang.SecurityException: PackageVerificationRslt: not allowed: pkg=app.revanced.android.apps.youtube.music, sha256=[818684e946ab7c1c298187f52f34455e15b386a07fa990d6c22268fab586ad60], atk=true, ver=241518018.true
05-13 23:48:19.109 E/mvo (19562): at android.os.Parcel.createException(Parcel.java:2072)
05-13 23:48:19.109 E/mvo (19562): at android.os.Parcel.readException(Parcel.java:2040)
05-13 23:48:19.109 E/mvo (19562): at android.os.Parcel.readException(Parcel.java:1988)
05-13 23:48:19.109 E/mvo (19562): at gns.a(SourceFile:14)
05-13 23:48:19.109 E/mvo (19562): at gmr.a(SourceFile:220)
05-13 23:48:19.109 E/mvo (19562): at gis.a(SourceFile:29)
05-13 23:48:19.109 E/mvo (19562): at giw.run(SourceFile:10)
05-13 23:48:19.109 E/mvo (19562): at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:462)
05-13 23:48:19.109 E/mvo (19562): at java.util.concurrent.FutureTask.run(FutureTask.java:266)
05-13 23:48:19.109 E/mvo (19562): at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
05-13 23:48:19.109 E/mvo (19562): at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
05-13 23:48:19.109 E/mvo (19562): at hdm.run(SourceFile:6)
05-13 23:48:19.109 E/mvo (19562): at java.lang.Thread.run(Thread.java:919)
The yt music apk version was 2.41.54 with armeabi v7a arch
Since I'm unable to patch it on armeabi v7a, so I patch it on arm64 v8a phone and transfer it to my v7a phone
For support, move to one of our links at https://revanced.app.
Bug description
This is not exactly a bug, but it is certainly not a feature request, and those were the only options to open an issue here.
Basically, I've noticed that, with the latest Manager app, the created YT Revanced apk triggers a Play Protect block when installing. The apk can be installed anyway, that's not a problem. But just a couple days ago I built the apk with what it was the latest version of the Manager back then (older than the current one), using the same base YT apk, and that apk does NOT trigger Play Protect. I have both apks in case anyone needs them to check them.
In addition to this, I don't think this is caused by some patch, I used the same patches both times (I checked).
I also tried some other fishy apks I have (not published on Play Store) and they do not trigger Play Protect, so it really seems like something has changed on newer Revanced Manager apps, rather than a Play Protect update.
It's not a big deal, but I would like to know for sure, or confirm, if something has changed, and/or if the devs are aware of it.
I hope this is not a duplicate, I tried to find info, but I only saw people with the same Play Protect problem, not a real answer as for why it didn't happen before. I also checked the Discord channel without success. Sorry if I missed anything.
Version of ReVanced Manager and version & name of application you tried to patch
Revanced Manager: v1.11.1 Base YouTube apk: 18.32.39
Installation type
Non-root
Device logs
Patcher logs
Acknowledgements