Android Question Error uploading .apk to Google Play "b4a.example already exists"

swabygw

Active Member
Licensed User
Longtime User
I'm ready to upload my first creation from B4A to Google Play. I created the .apk file by running it in Release (obfuscated) mode. Got the following error when uploading to Google Play: "You need to use a different package name because 'b4a.example' already exists in Google Play." I did a Clean Project, searched my modules for any references like this, but can't find anything. Any ideas?

(screenshot attached)
 

Attachments

  • google_play_upload_error.jpg
    google_play_upload_error.jpg
    23.2 KB · Views: 163

mangojack

Expert
Licensed User
Longtime User
IDE menu > Project > Build Configuration > Package Name. Should be something unique .. ie com.swabygw.myappname
 
Upvote 0

swabygw

Active Member
Licensed User
Longtime User
Thanks, I changed it as directed which, although, it solved the problem of being able to upload it to Google Play, when I recompile/run in any mode (Release, Debug, etc.), I'm getting a new error that access to the path of the .apk file is denied (I'm using B4A v5.50 and have the project stored in a Documents subdirectory). I tried right-clicking on the .apk file and reclaiming ownership of the file, but it seems that permission is denied to do that. Looks like it won't let me delete the file, either.

UPDATE: Rebooting my machine seems to have solved the problem - after reboot, the .apk file was gone and I could recompile. Thanks for your help!
 
Last edited:
Upvote 0

mangojack

Expert
Licensed User
Longtime User
I can only suggest restarting your pc / laptop .. if you have not already done so.
is your Documents folder located in a Google Drive folder ?
 
Last edited:
Upvote 0

swabygw

Active Member
Licensed User
Longtime User
No - I tried copying my project to another folder (without the .apk file) and the worked for one compile and, then, the newly-created .apk was locked again. Rebooting removed the file again. Something about changing Package Name did it. It's odd...but, rebooting gets it done.
 
Upvote 0
Top