I've been trying to upload my first app to Google Play but I'm having a problem. Using the old style dev console I seem to be able to upload my app ok. I then enter a description, title etc. and hit save and get 'unexpected error'.
I've read a lot about people having this problem and tried various things but to no avail.
So tried using the new style dev console. Description can be entered and screenshots uploaded and saved just fine. Go to upload my app and get to this point...
My app neither needs nor requires an expansion file as it is well under the 50mb limit (it's under 220kb) and requires no external files. It doesn't have any licensing either.
I've been in touch with google a couple of times and they've gotten to the point of asking me to test my apk with the aapt tool to see if it has any errors. Done that, no problems. Sent them back a copy of the apk with the 'aapt dump badging' output. That was four days ago. Not heard anything back so thought I'd come here and ask for help.
I'm able to install the app to my phone directly (copying the apk from pc to the download folder on galaxy s3 then clicking on it on phone to install it) with no problems.
I did search the forums here before posting this but couldn't find anything specific to this.
I'm hoping someone else using b4a has had this problem and can help me with a solution. Or at least tell me if I'm having a Homer style D'oh moment and missing something really obvious.:signOops:
Will post code or attach APK if necessary.
Thanks in advance.
I've read a lot about people having this problem and tried various things but to no avail.
So tried using the new style dev console. Description can be entered and screenshots uploaded and saved just fine. Go to upload my app and get to this point...
My app neither needs nor requires an expansion file as it is well under the 50mb limit (it's under 220kb) and requires no external files. It doesn't have any licensing either.
I've been in touch with google a couple of times and they've gotten to the point of asking me to test my apk with the aapt tool to see if it has any errors. Done that, no problems. Sent them back a copy of the apk with the 'aapt dump badging' output. That was four days ago. Not heard anything back so thought I'd come here and ask for help.
I'm able to install the app to my phone directly (copying the apk from pc to the download folder on galaxy s3 then clicking on it on phone to install it) with no problems.
I did search the forums here before posting this but couldn't find anything specific to this.
I'm hoping someone else using b4a has had this problem and can help me with a solution. Or at least tell me if I'm having a Homer style D'oh moment and missing something really obvious.:signOops:
Will post code or attach APK if necessary.
Thanks in advance.