Can't upload new build due to "The apk is signed with different certificate"
It has been many months since we have uploaded a build to our Alpha Channel. Today I try uploading and get: 'The apk is signed with different certificate than previous version'. Of course, we have NOT changed our certificate - ever. Any thoughts on what else could cause this? Previous uploads were done through the website (deprecated) or the Oculus Platform Tool in Unity. Trying this build through MQDH. Any suggestions would really help my blood pressure!
APK Not Signed On Upload To Release Channel
I am getting an APK not signed message on build upload to a consumer release channel on Oculus Dashboard, however it was working, details below. This is the output from apksigner Verifies Verified using v1 scheme (JAR signing): false Verified using v2 scheme (APK Signature Scheme v2): true Number of signers: 1 I have no problem with Unity 2019.4.19 using the Standard Utilities Plugin and the previous Oculus Integration (not sure what it was but not 23.1) However, I am now using 2020.2.4, with XR Plugin Management 3.2.17, Oculus XR Plugin 1.7.0 and Oculus Integration 23.1 The application builds and works on the Quest, but whether I build via Unity, export to Android Studio and build there or even export and force Android Studio to sign the application using Generate Signed Bundle/APK, I get the same error. I have tried a new Keystore, checked gradle files and a variety of other items. The build settings are pretty much the same as in 2020 to 2019, so I am at a loss. Any ideas?
Quest + Unity 2019: APK Signed with Signature Scheme V1
Hi, I'm building an apk from Unity 2019.1.0f2 and when I upload to my build dashboard I keep seeing this error: After doing some research it looks like any version of Unity after 2017.1 should be building with V2. I'm assuming something is old as I'm coming from older Unity versions or maybe something is being overwritten on export...? I've tried creating a new keystore and reworking/updating the android manifest with no luck and the build sideloads and runs great. Before I go down the route of exporting to gradle and building from android studio, does anyone know where I should be investigating? It'd be awesome to not have to add that extra step. Lastly, in the docs it says you can sign as v1 if you're targeting GearVR/Go/Quest in one build (or at least it appears that way) so maybe this is an erroneous error? Thanks!
