This topic describes how to generate a Meta 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 Meta 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.
Meta Quest native APKs must be signed using the v1 and v2 signing scheme. The following are instructions on how to produce a compliant APK:
Note: You need to compile using Android SDK 26 or higher for headtracking, but your minimum SDK must use Android SDK 23 or above in order to run on Meta Quest. We recommend setting minSdkVersion to 29 to match the OS version of Meta Quest.
In Android Studio, go to Build > Generate Signed Bundle / APK. This will walk you through the process of generating a signed APK file.
On the first screen, select APK and click Next.
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.
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.
Once complete, the signed APK will be in the destination folder you selected.
