I've just got a new Android 14 device, and I'm wondering if I'm missing anything. Last week, I released an update to my app via Google Play, and installed that on the device through the store.
This week, I'm working on the updates for next month's API level changes, so I've set up B4A Bridge for the first time, and granted it permissions.
On attempting to install a build:
1. I get a question asking if I want to update from Bridge, because this is normally updated via Play. I tap update Anyway.
2. The install progress shows
3. I get a Play Protect pop-up, App scan recommended, and tap Scan app. This confirms it looks safe.
4. I tap Install on the Play Protect pop-up and get the message "App not installed as package conflicts with an existing package"
This is the bit I don't understand; the package name is exactly the same - nothing's changed. So it appears to be refusing to let me update via Bridge, after first making me jump through all those hoops. Is this something to do with keys? Again, I've not changed anything, but obviously the version via Play is signed using the managed key process, and I've never had this problem before.
The same happens regardless of whether I'm building in release or debug modes.
It's three years since I last bought a new phone, so perhaps I've forgotten some step, but I don't think so...
This week, I'm working on the updates for next month's API level changes, so I've set up B4A Bridge for the first time, and granted it permissions.
On attempting to install a build:
1. I get a question asking if I want to update from Bridge, because this is normally updated via Play. I tap update Anyway.
2. The install progress shows
3. I get a Play Protect pop-up, App scan recommended, and tap Scan app. This confirms it looks safe.
4. I tap Install on the Play Protect pop-up and get the message "App not installed as package conflicts with an existing package"
This is the bit I don't understand; the package name is exactly the same - nothing's changed. So it appears to be refusing to let me update via Bridge, after first making me jump through all those hoops. Is this something to do with keys? Again, I've not changed anything, but obviously the version via Play is signed using the managed key process, and I've never had this problem before.
The same happens regardless of whether I'm building in release or debug modes.
It's three years since I last bought a new phone, so perhaps I've forgotten some step, but I don't think so...
