All Oculus Quest developers MUST PASS the concept review prior to gaining publishing access to the Quest Store and additional resources. Submit a concept document for review as early in your Quest application development cycle as possible. For additional information and context, please see Submitting Your App to the Oculus Quest Store.
If you want to upload your app package to the Oculus Store, the app manifest (
AndroidManifest.xml) for your Android app must conform to the Oculus specifications described in this topic.
This topic contains following sections:
Find general requirements for your app’s
AndroidManifest.xml file in Android Manifest Settings in the native development guide.
For release in the Oculus Store, your app’s manifest should also meet the following requirements:
For Quest and hybrid apps - Enable the headtracking feature per signing requirements of the app. For more information, see Application Signing.
<uses-feature android:name="android.hardware.vr.headtracking" android:required="true" android:version="1" />
<uses-feature android:name="android.hardware.vr.headtracking" android:required="false" android:version="1" />
The package name should contain your company name and the app name. It cannot be the default value or be copied and pasted from another app. In addition, it must not be shared with any other Oculus Store app. For example, the Oculus Venues app could have a package name of
android:label must contain the name of the app or a reasonable representation of the app name, and the label must be unique in the Oculus store.
installLocation must be set to
versionCode must be greater than the value used in a previous build of this app.
android:debuggable value must be
false. Your app must be a release version, not a debug version.
android:compileSdkVersion must be set appropriately. API versions greater the minimums specified prevent users from installing your app. For previously released app, use caution when changing the
minSdkVersion as you may break compatibility for users on older versions of Android. For apps that target both Quest and Go/Gear with the same APK.
minSDKVersion should be lower of the values, but the target and compile versions must align with the higher Quest values.
Following are the accepted values for
compileSdkVersion by device:
Specify the correct
intent category for the MAIN action:
android.intent.category.INFO, and NOT
android.intent.category.LAUNCHERso that your app appears only in Oculus Home and not the device launcher.
excludeFromRecents value should be set to
Note: Apps must specify
installLocation="internalOnly"or be rejected by the upload validator. This accommodates installing apps on SD card external storage. If you have a special circumstance and require a different install location setting, contact the store team using the Get Developer Support form.
The Unity Android project settings let you set some of the required application manifest options for building a mobile app suitable for the Oculus Store. To set the remaining manifest settings, use the Oculus Utilities for Unity 5 plugin or edit the manifest directly.
The steps below describe how to configure Unity to build Oculus Store-compatible Android .apk packages.
Note: These steps only work for Oculus Utilities for Unity 5 version 1.10 and later.
Set Minimum API Level to the following depending on your target device:
Unreal Engine ignores the Android project settings options when building mobile apps and instead uses instructions in an XML file to create the application manifest file. This XML requires a small modification to make builds suitable for the Oculus Store.
The steps below describe how to configure Unreal Engine to build Oculus Store-compatible Android .apk packages.
The following VRCs describe the store requirements for app manifests.