Welcome to the Oculus Developer Forums!

Your participation on the forum is subject to the Oculus Code of Conduct.

In general, please be respectful and kind. If you violate the Oculus Code of Conduct, your access to the developer forums will be revoked at the discretion of Oculus staff.
New to the forums? Click here to read the How To guide. -- Developers click here.

Signature Versions V1 & V2. Unity 2017.3.1f1

Plague.NeilPlague.Neil Posts: 5 Oculus Start Member
Hello,
I have been pumping out early versions of my game for the Go on the Oculus site for a while now, with no troubles. But now suddenly it is telling me that my game is signed with V2 Signature scheme. I don't understand what has happened in Unity to change this. Anyone have any ideas? I looked through forums here and on through the android docs and it is saying to change info in the build.gradle file, but not how to find it.
Any better references or links would be awesome.
Thanks,

Comments

  • imperativityimperativity Posts: 3,587 Valuable Player
    Hi,

    Can you try Unity version(s) 2017.1.0p5 or 2017.2b8 as there is a fix pushed to address this issue in these releases.
  • imperativityimperativity Posts: 3,587 Valuable Player
    @Plague.Neil

    If you aren't able to change your Unity version try the below work-around for signing your project.

    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.

  • Plague.NeilPlague.Neil Posts: 5 Oculus Start Member
    @imperativity I have the build set to internal, but I think at some point I must have changed it to Gradle for no reason at all and changed it back to internal. I am currently going through: without any luck so far.

  • Plague.NeilPlague.Neil Posts: 5 Oculus Start Member
    Finally got the thing to sign as V1, I have to jarsign it through cmd console everytime, but it works.
Sign In or Register to comment.