That's what it looks like, but I followed the very simple instructions... I thought. Thank you both for your replies and consideration....and further help/. I'm quite at my wits end about this. My app (test version, but I'm still rushed) should have been up for testing days ago
OK. What does this have to do with Android Studio and with this package name?
Is it a new app that hasn't been published on the Play Store yet?
<<Is it a new app that hasn't been published on the Play Store yet?>>. yes
OK. Then there must be at least a draft of the app in the Google Play Developer console,
because of this:
yes....most all were uploaded using a different file name, but certainly much of the contents was the same as the others
Read my last post.
And post a screenshot like this:
i found a page similar to yours. it had a draft app, which i deleted. will try again
Fine,
- build your app as AAB on the AI2 test server (which targets SDK 31) and
- try to upload it to the Play Developer console as an internal test track and
- if you do not get an error wait for the Pre-launch report ...
If you get an error we will see what to do ...
<< build your app as AAB on the AI2 test server (which targets SDK 31)>>
i didn't know this test server existed. I'm getting the same error
Do I have to manually set something to target 31? Thanks so much for your help....impatiently awaiting your reply. I really need to get through this bottleneck
This shouldn't happen. Are you sure you used the test server?
Build the APK, upload it to Google Drive and post the link.
link to apk and aab
https://drive.google.com/drive/folders/1e4SHypg7GowNRsCXcGMorrGB6bxLkTCB?usp=sharing
OK looks fine.
I built an AAB on the test server and get this in the Manifest:
So this error should not appear when you upload the AAB in the Play Developer console.
