APK is signed with Signature Scheme V3, which is not yet supported. Oculus platform

Target Platforms XR
1

Hi,

Surprise ! today I try to upload a new build on Oculus platform and this message appear:

APK Signed With Signature Schema V3
APK is signed with Signature Scheme V3, which is not yet supported. Please disable signing with Scheme V3 and upload again.

I always published build (24) with same project and setup…

https://screencast.com/t/Owk5ggRklE

How to correct this ? it’s unity problem signing ?

Best

2

Work if I change internal to gradle build… why ? it’s Oculus magic !! … :rage:

3

Wow, I just had the same issue, and like you I’ve always been using the same project and setup. WTF ?

Edit : I’m not as lucky as you, my Grable builds always seems to fail, not sure why…

4

Hum. Same problem here. 2018.2.5f1.

Already uploaded several times one month ago without any issue with internal build method but now the Oculus tools command tells me the app is signed with V3 and need to be signed with V2.

if I check the apk with apksigner I got:

Verified using v1 scheme (JAR signing): true
Verified using v2 scheme (APK Signature Scheme v2): false

Does that mean the apk signature is not even in v2 ?

Gradle is not building the app. I will try to fix that first.

5

If you fix that, could you explain how you did it ?

6

Just had the same issue. Made a build in December using unity 2018.2.6 and uploaded fine. Made build today with same version of Unity and getting the V3 message :o

Not yet attempted Gradle option

7

I tried to make Gradle work, but it keep failing. I guess I’ll manually push the .APK files for now…

8

Gradle fortunately worked for me with my app (simply selected it, didn’t have to do anything else).

It may well be that Decembers version also was set to Gradle after all, turns out someone here and switched it to Internal recently

9

Could you tell me the steps do make Gradle work ? I’m still stuck on that step :frowning:

Edit : Ho, ok, worked by default, argh!

10

For me neither the gradle works nor the app is getting uploaded because of the v3 signature schema. Don’t know how to resolve this error. Can anyone help me?

11

I opened a topic on the Oculus forum, no answer so far : https://forums.oculusvr.com/developer/discussion/72775/apk-is-signed-with-signature-scheme-v3-which-is-not-yet-supported#latest

12

Follow this video for app signing. It works for me. :smile:

1 Like
13

Hi. Managed to make a gradle build by uninstalling Android NDK from Android Studio. See there https://discussions.unity.com/t/715857 .

Now build is ok, upload on the Oculus is OK, but do you guys take into account this message from Oculus on the Unity TroubleShootings about the grable build ? https://developer.oculus.com/documentation/unity/latest/concepts/unity-troubleshooting/

It tells us :

All Unity 2018.2 versions

  • (Mobile) You’ll need to either switch the AndroidBuildSystem to internal or export a Gradle project and modify the SigningConfig in the build.gradle file to include v1SigningEnabled=true, v2SigningEnabled=false.

Fun time!

14

Thank you so much, I made it work with this. You, and the guy on the video, made my day !

2 Likes
15

Oh nice. I give it a try.

16

yup it works :slight_smile: I am glad i helped you.

17

I had this problem today and after downgrade the Android SDK the problem is gone when i make internal builds.
I’m with the 27.0.3 SDK version now.

1 Like
18

I have this problem with signing scheme v2 for Oculus Quest.
I am using Unity 2019.3.0f5 and Oculus XR Plugin 1.1.5

I have tried to disable v2 signing (and force back to v1) via

android {
  ...
  signingConfigs {
    config {
      ...
      v2SigningEnabled false
    }
  }
}

I have even tried building the APK with Android Studio.
I have tried uploading to Oculus build manager via web, and via ovr-platform-util.exe.

Oculus continues to report that: APK is signed with Signature Scheme V2, which is not yet supported.

Please help.

19

What exactly is your issue? this thread was originally about v3 error. Why are you trying to force v1 if you are targeting Quest?

20

@carsonherrick did you ever figure it out?
@Ostwind - imho it’s relevant since the issue is really about controlling the signing scheme, whatever it may be…