So the project I’m referring to is the brand new build. Every single time you download source code, it’s like a brand new app. When you go updating the old version on the Play Store to your newest source code version of the app, you’ll have to open up the new app project you just downloaded on your machine, in Android Studio. It won’t sit within the old project or anything like that. It’s like it’s a brand new app. It’s basically like a duplicated version of the old app, but now has your newest changes in it.
You download the new app build from Dropsource onto your machine. When you go open an “existing project” in Android studio, it’s just referring to an app that’s already in the process and created as opposed to Android Studio creating a brand new app from scratch.
So you’ll Build your project in Dropsource, download the source code, know where it’s saved (heck you can delete the old version on your computer since it’s pretty much moot now), and open that new project in Android Studio from the top most folder of it. Then make that version numbering adjustment like we talked about… then follow the deployment process in the help resources from start to finish with the caveat being that you’re updating the app in Android Play Store. Android Play Store will notice that they are the same projects and will also see the incremented build id (because you changed it manually before archiving your project in Android Studio) and it will overwrite what’s in the Play Store now with your new app project. Then you’ll go to the Play Store and download the update. This will then overwrite the app that used to be on your phone with the new 1 you just downloaded from the Play Store. At that point, you have the new app on your device.
@cchute correct me if I have that wrong at all please but that’s my understanding. Also Carl, there’s no need to make any adjustment to the bundle id or anything for the new app project Trevor gets when he downloads his latest build’s source code from Dropsource, right?