Gear VR - do I have to recompile every time I add an OSIG file?

I am developing using my own Gear VR device, I know how to generate the OSIG file using the instructions in the docs, and everything is fine. Unfortunately, after a demo with my delighted client, 3 different people came to me with 3 different devices (one at a time, of course), asking me to install the demo on their devices. Putting the devices in debug mode and generating the osig files was not big deal, but opening the editor and redoing the build everytime is a time-consuming activity.

Opening the apk I’ve seen that the osig files are stored in the assets folder, so I tried pushing the new osig file in that place, but it did not work.

Is there a way to enable a new Gear VR device without having to rebuild the whole project from start?

Heya!

You need to get signature files for every device you want to build to but on the upside, you can stick them all in your Assets folder and one build will work for all:

I looked at the Oculus documents and right now they only give Unity the power to create debug signature files. :frowning:
Please, Epic! Fight for that functionality for us!

Yep, I know, thank you anyway! :wink: currently my assets folder contains half a dozen signature files. I just hoped I could avoid the build! Alas I cannot (the osig file reference is embedded in the Android Manifest. I read it somewhere, can’t find the link anymore)

I know this is an old question but Oculus has done a lot since you posted this.

Oculus Keys is the solution you’re looking for:
https://developer3.oculus.com/documentation/platform/1.2/tasks/dg-keys/

Oculus forum discussion on Keys:

Awesome, thank you for letting me know! :slight_smile: