Android Question I want to confirm that "Play app Signing" is on a per-app basis and not account-wide?

[JohnC]

I have an older app that was first built using NSBasic and used an old 1024-strength key to sign it and upload to the play store.

Then, back in 2015, I created a totally new version of the app using B4A and I was able to use command-line tools to sign it with the older key and the play store accepted it.

As per Google's rules, I now need to upload a new version that has the target SDK set to 34 so that the app will be visible to "new" users.

I tried the command line tools to resign the app, but the pay console is rejecting it for various reasons.

So, the thought came to me that maybe I can switch *just this app* to use the new Play App Signing so that I won't need to use the old key and can use a new key to upload it to the play store.

But, I heard that opting-in to the Play App Signing is not reversible, and I am OK with that as long as it is just for this ONE app, and not switch all my other apps to Play Signing.

So, I am just looking for someone to confirm that if I opt-in for Play App signing for this ONE app, it won't effect my other apps in my play store account.

 

[Erel]

I have several apps in my account. Most of them use play app signing but not all of them:

 

[JohnC]

Thank you for that confirmation

 

[asales]

Same as Erel and I use 3 options on the same account.
For old apps (apk) I use the old key. For new apps (aab) I use the keystore file and the Google signed option.