Android Question Installing new app using B4A bridge overwrites existing but different app developed with B4A

[Acuario]

Hi,
I have an app I developed and installed in release mode with B4A using B4A bridge on my phone. It all works fine.
Now I am developing another B4A app. It has a different name and the ApplicationLabel is different in the project attributes so has nothing in common with my other app.
When I run the new app using the B4A bridge either in Release or Debug my original app gets replaced by the new app.
How can I avoid this? Why is it happening?
Thanks

 

[Cableguy]

You need to change the name of the app from "example" to what ever you want it to be, and also change the publishing key, they are unique to each app

 

[JohnC]

The "Package" name (IDE...Project...Build Config) needs to be unique for each app you write.

 

[Acuario]

Thanks, changing the "Package" sorted it out but interesting about the publishing key - I haven't published anything on Google Play but will keep that in mind.

 

[KMatle]

Thanks, changing the "Package" sorted it out but interesting about the publishing key - I haven't published anything on Google Play but will keep that in mind.

The key represents "you" as a developer and is always the same for every app. Only with the same key you can upload a new version. The package name (similar to a file name) must be unique and different for each app but keep in my that this means for ALL apps in the world (=unique package name worldwide). Mostly you use a name like uk.acuariosmith.yourappsname for your packagename.

 

[Acuario]

Ok, thanks, got that.
The problem I now have is using my own key I can't install the app on my phone using B4A-Bridge as detailed in #6 here https://www.b4x.com/android/forum/threads/blocked-by-play-protect.114898/

 

[JohnC]

You might need to turn off Play Protect (from within the Play Stores app's settings).

Then down the road when you successfully publish your first app in the play store, google will then know your "private" key and should recognize you as a developer from that point on.

 

[JohnC]

Another reason you may not be able to install the new app is that you have the previous app installed (that has the same packagename) but was signed with the old key.

If this is the case, then just uninstall the previous version of the app and then try doing a clean install of the new app so everything is in sync.