Or, how we crafted our AndroidManifest.xml manifest superfile from completely shaky and hidden online documentation rumors.
It took us waaaay too long to hunt down all the details of how to get our Android demo from a side-loading APK into a fully functioning app that would play nice with the Oculus launcher app on GearVR. For those on the same journey, we;re sharing the key resources:
Mobile Build Target: Android : SETTINGS DETAILS
Oculus Submission Validator
a nasty little piece of command-line software that will save you many many headaches:
Application Manifest Requirements
bits and pieces of what you need to insert into your XML manifest
outdated but still informative :
Oculus Mobile Submission Guidelines PDF
more general knowledge:
Unity VR Overview 5.1+
porting Unity projects from Oculus SDK (0.5.0 or prior)
to Utilities for Unity (0.1.2+ on Unity 5.1+)
For those who have been building VR for a year or more, and want to update your projects from legacy Oculus SDKs and Unity 4.6 into the present:
1. what to delete when you port
2. whats in the Uilities package
general unity forum for VR Q&A
possible 45 minute detail video session if all else fails:
Your Golden Ticket:
SAMPLE AndroidManifest.xml
First you need to copy your custom Android manifest here:
Assets/Plugins/Android/AndroidManifest.xml
You can copy the Android Manifest that Unity generates when you compile your game,
it’s on folder:
YourProjectname/Temp/StagingArea/AndroidManifest.xml,
copy from there to
Assets/Plugins/Android.
Have fun, kids.