In Unity 2017 android apks are signed using Signature Scheme V2, however if the app is a VR app for the Oculus Gear VR store it can only be signed using Signature Scheme V1. This means any GearVR apps built using Unity 2017 get rejected when being submitted to the store, Oculus say they do not plan on allowing Signature Scheme V2 signed apps any time soon so it would be great if Unity allowed the option to choose how the apk is signed.
Allow the option to choose Signature Scheme V1 for Android in Unity 2017
Oct 06, 2017
For now, GearVR builds are using signing v1, starting with 2017.1p5, 2017.2b8 and 2017.3a3.
When Oculus supports v2 in their store, we'll switch to using v2 again.
Your opinion counts
Help us make things better. Share your great idea for improving Unity or vote for other people’s.Log in to post a new idea
- Server Time Function
- Unity Analytics Quick Date Range Selection
- Allow use of StackTraceLogType.None in Unity Cloud Builds
- Use "Unity" to make "Game Design Document"
- Buy other asset store packages directly with my publisher account revenue