I am trying to update an app I have on the store, which has proved to be somewhat problematic.
First I compiled an apk, which was rejected for the following reason.
Quote: "The app is published as an apk that supports TV. In other words, it contains <category android:name="android.intent.category.LEANBACK_LAUNCHER"/> under one of the intent-filter of the main activity . It must be published as an app bundle instead."
No bother, I thought, I'll just compile it as an .aab file instead and try that. It didn't take long to create the file and upload it, only to be met with the following error...
Quote: "To upload an Android App Bundle you must be enrolled in Play App Signing."
*sigh*
Ok, so this is already taking much longer than I had hoped it would. Surely signing up to Play App Signing can't be much of a hassle can it?
It can.
It can indeed...
I chose the "
Use existing app signing key from Java KeyStore" option, which is the only one which isn't hidden as an "advanced option".
It took longer than I care to mention to figure out how to enter the line of Java the Console provides, but it seems to need an Alias? Which my keystore doesn't have. When compiling .apks previously I have always left the alias boxes on the compilation dialogue blank.
The next option down, and the first of the "Advanced options", was "
Use existing app signing key from another repository". The instructions for this one made a lot less sense.
The final option was "
Use a new app signing key (this requires ongoing dual releases)", which I think I would rather avoid.
Can anyone please help me with this? I need to get this app updated as soon as possible.
Thanks in advance.
