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.
We're no longer accepting submission of 32-bit Oculus Quest apps. Any new or updated Oculus Quest application needs to be 64-bit. Please contact Oculus if you are unable to comply with this policy. Oculus Go and Gear VR apps will not be affected by this change.
This topic describes how to generate an Oculus Quest APK signed with the Android v2 signing scheme.
You must sign the release version of your app with an Android certificate before you submit it for review.
Android uses a digital certificate (also called a keystore) to cryptographically validate the identity of application authors. All Android applications must be digitally signed with such a certificate in order to be installed and run on an Android device.
All developers must create their own unique digital signature and sign their applications before submitting them to Oculus for approval. For more information, see Sign Your App in the Android documentation.
Make sure to save the certificate file you use to sign your application. All subsequent updates to your application must be signed with the same certificate file.
Oculus Quest native APKs must be signed using the v2 signing scheme. The following are instructions on how to produce a compliant APK:
Add the following to the Android manifest:
<uses-feature android:name="android.hardware.vr.headtracking" android:version="1" android:required="true" />
Note that you will need to compile using Android SDK 26 or higher for headtracking, but your minimum SDK must use Android SDK 23 in order to run on Oculus Quest, so make sure the minSdkVersion and compileSdkVersion are properly set.