Search Feedback

63
votes
Completed

Allow the option to choose Signature Scheme V1 for Android in Unity 2017

Platforms

-

-

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.

Response avatar

Yury-Habets

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.

Comments (2)

  1. 081f28ccf55646e6fe54c9c2aa890aca?d=mm

    Yury-Habets

    Oct 06, 2017 09:44

    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.

  2. Ad49b6671ac43cdc6a644d6e89b361d7?d=mm

    RiccardoAxed

    Aug 29, 2017 13:45

    I've the same problem too, right now it's impossibile to publish a Gear VR Unity app on the Oculus Store because of the unsopported signature scheme V2. It would be crucial for Unity to have the option to choose between V1/V2 signature scheme.

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

Categories

All

(9353)

2D

(241)

Ads

(43)

AI & Navigation

(71)

Analytics

(106)

Animation

(330)

Asset Store

(243)

Assets

(497)

Audio

(159)

Cloud Build

(102)

Collaborate

(33)

Docs & Tutorials

(203)

Editor

(2160)

Everyplay

(13)

Game Performance Reporting

(15)

General

(831)

Graphics

(790)

GUI

(373)

Input

(149)

Licensing

(77)

Networking

(163)

Physics

(349)

Platforms

(413)

Profiling & Optimization

(72)

Runtime

(164)

Scripting

(1044)

Terrain

(151)

WebGL

(134)