Will PiracyChecker still work with Android App Bundle?
drmrbrewer opened this issue · 4 comments
What parts of PiracyChecker will still work (or which parts won't) for an app that is published with the Android App Bundle?
Everything works the same with app bundles
@jahirfiquitiva I thought that with the Android App Bundle method, it is required also to enable Google Play App Signing (see the link in my original post). And according to the docs for PiracyChecker, the signature checker method will not work with App Signing enabled?
uhm, yep, you're right. that specific thing won't work with app signature enabled. all other methods would still work, though.
anyways, iirc, i actually think you can upload bundles that you signed yourself, i think i've done that, but you'll probably want to give it a try yourself
@jahirfiquitiva I've now started using the App Bundle publishing method (since Google will soon be forcing this anyway). Now that I understand the App Bundle process a bit better, I'm wondering whether the signature part of PiracyChecker might still work?
To opt in to App Bundle (and App Signing), we have to upload our current app signing key to Play Console, so that the same key is still used to sign the apk? The "only" change is that Google now generates and signs the apk (using the App Bundle), but the same signing key is being used?
When opting in to App Bundle, you can also generate a new "upload" key that is used to sign the App Bundle that is sent to Play Console, and yes the "upload key" will effectively be removed and replaced by the "signing key", but the crucial point is that the "signing key" is the same as it was before... hence so long as we continue to use the "signing key" to set up PiracyChecker in our code, and not the new "upload key", it will all still work OK?