Oculus Quest Development

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.

Android Application Signing

Oculus mobile apps require an Android application signature file in order to be submitted to the Oculus Store.

Android Application Signing

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 and instructions, please see Android’s “Signing your Applications” documentation: http://developer.android.com/tools/publishing/app-signing.html

Make sure to save the certificate file you use to sign your application. Every subsequent update to your application must be signed with the same certificate file, or it will fail.

Note: Your application must be signed by an Android certificate before you submit it to the Oculus Store.

Android Application Signing and Unity

Unity automatically signs Android applications with a temporary debug certificate by default. Before building your final release build, create a new Android keystore by following the “Sign Your App Manually” instructions in Android’s Sign your Applications guide. Then assign it with the Use Existing Keystore option, found in Edit > Project Settings > Player > Publishing Options. For more information, see the “Android” section of Unity’s documentation here: http://docs.unity3d.com/Manual/class-PlayerSettings.html.

Android Application Signing and Unreal

Before building your final release build, create a new Android keystore by following the “Sign Your App Manually” instructions in Android’s Sign your Applications guide. Once you have generated your distribution keystore, go to Edit > Project Settings > Platforms > Android, scroll down to Distribution Signing, and entered the required information.

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:

  1. 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.

  2. In Android Studio, go to Build > Generate Signed Bundle / APK. This will walk you through the process of generating a signed APK file.
  3. On the first screen, select APK and click Next.
  4. On the next screen, create a new keystore or choose the path to an existing one. If you are creating a new keystore, the other fields should fill in by themselves once you create it. If you choose an existing keystore, enter the appropriate information. Click Next to continue.
  5. On the final screen, enter the destination folder for the APK, select the build variant if necessary, and check V2 (Full APK Signature). Click Finish and the build will begin.
  6. Once complete, the signed APK will be in the destination folder you selected.