Skip to main content
Inpu
Up and Coming
January 16, 2019

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

Hi,

I have this error since this morning using the command tool to upload APKs. It was working fine yesterday. I've always been using the same build and project since the beginning. Is something going on ?

It seems I'm not the only one (https://forum.unity.com/threads/apk-is-signed-with-signature-scheme-v3-which-is-not-yet-supported-oculus-platform.613405/).

Thanks

This topic has been closed for replies.

17 replies

InpuAuthor
Up and Coming
January 16, 2019
There's more people impacted by the hours on the Unity thread. For some a Gradle build is working, but I'm unable to make a Gradle build for some reason. Please help :(
InpuAuthor
Up and Coming
January 16, 2019
Managed to make a Gradle build, but now it's telling me that I should use the same key as for my previous build, so I guess that won't be an option !
wraithwon
Up and Coming
January 16, 2019
I am having the exact same issue. Just uploaded fine a day or two ago, nothing changed in my process.
InpuAuthor
Up and Coming
January 16, 2019
I finally made it work using jarsigner thanks to a tips on the Unity topic ! Today has been a crazy ride for many dev it seems :/
davidppp
New Participant
January 17, 2019
We were able to successfully avoid this error by uploading an apk built with Gradle (via Unity Build Settings).
wraithwon
Up and Coming
January 17, 2019
I switched from internal to gradle and it started letting me upload again. The real mystery is why did this suddenly started happening despite no change in my build process or unity version?

PS: I was getting a weird MIPS architecture error when I switched to gradle that caused it to fail to build. I went in an renamed (or delete) my android ndk folder and it fixed that error.

Anonymous
January 17, 2019
Experience the same . I thought this had to do with my Java SDK update to V1.8.0_202 which i did before the build . Did you guys update ( or let it autoupdate ) Java too before ?
Anyways - i was able to fix my issue by using the jarsigner ( from the JDK bin folder ) to resign the apk with V1 scheme.
The syntax ( commandline, though i made a batch script which lets me drag and drop the apk onto it ) for this would be:
jarsigner -verbose -sigalg SHA1withRSA -digestalg SHA1 -keystore <KEYSTORE> -storepass <STOREPWD> -keypass <KEYPWD> <APKFILE> <ALIASNAME>
The parts in bold ( including the enclosing  <...> ) should of course be replaced with your specific values


mousebear
mousebear
Honored Contributor
January 18, 2019
Thanks for the heads up, I've notified our engineering team and will update you all here once there is progress.
If you need immediate help or want additional support/context on an issue you are having with our platform or integrations: 1. Gather any and all logs , screenshots, and version numbers of relevant software (Oculus SDK, engine, etc.) 2. Please submit a ticket here through the "Contact Us" link (include what you've gathered in step 1). 3. Tag me @mouse_bear once you have done so!
SteveHexapuss
Inspiring
January 19, 2019

spacefrog said:

jarsigner -verbose -sigalg SHA1withRSA -digestalg SHA1 -keystore <KEYSTORE> -storepass <STOREPWD> -keypass <KEYPWD> <APKFILE> <ALIASNAME>
Thank you spacefrog, you are awesome.
Your workaround worked for me. 
Gifgroen
New Participant
January 21, 2019
My guess would be that there was an Android sdk update that enforced this behaviour? That's the only variable in this case if you ask me. Did somebody else update there Android Studio or Android SDK after which this started happening?
Show more replies
Terms & ConditionsAccessibility statement