UPDATE 20th April 19:15:
It appears the same issue with the token regenerisation is still happening :(
The latest version of the app installed okay with the new permission after uninstalling.
The only reason I can think of for the 'different signature' problem to have happened, is if I had uninstalled the clover signed app, and reinstalled directly from a sideloaded version. However I'm using the same signing for both, so I'm not sure how that works either?
Original Question 20th April 19:00:
My sandbox clover app updater is failing for a new version of my APK I'm getting this on logcat:
W/PackageManager: New package has a different signature: <my apps package name...>
I initially uploaded an APK via the sandbox clover website, and installed to get permissions to use the API.
I have since been sideloading, but now need to add to the permissions, so I've checked the new ones and uploaded a new APK with the same signing and key. The upload works fine, and even reaches the App Updater app on clover mini (real physical dev kit) but almost instantly shows 'Install Failed'
I have tried:
- Another signing to see if it was that, but as expected I couldn't even get the APK to upload as they didn't match
- Signing with only v1 signing ticked in the new android studio signing options (It now allows v2). This also didn't change anything
- Multiple restarts and app updater and app store cache clears (Until I found the log above confirming it was something specific)
I have yet to try an uninstall, as I recently hit an issue with token regeneration after an uninstall.
I'll probably trigger it now, and hope that issue is faster than 24hrs this time. I'd still love to know if i'm doing something wrong here, and whether there's anything I need to know about updating permissions on production after an initial app release.