Meta Developers

The Meta XR Core SDK provides a mechanism to directly upload the app from Unity to the Meta Quest Developer Dashboard. Using the tool, you can upload development builds to release channels as needed.

Understand app components

An app contains build and metadata. Meta Quest supports two types of apps: Quest and Link PC-VR. A Quest build contains an APK file and optional OBB and asset files. A Link PC-VR build folder contains an executable file and optional asset files. Asset files, which are generic infrastructure, are used for adding content, DLC, extra content, and access to the optional asset files. Metadata includes information such as app name, screenshots, description, and content rating. Most changes to established metadata require Meta Quest review.

Upload build

You can upload builds in several ways such as through the developer dashboard, command line interface, or directly from Unity using the OVR Platform tool. The following instructions describe the process of uploading the build from Unity:

Upload Meta Quest builds

On the menu, go to File > Build Settings > Build to compile the build.
After the build is compiled, on the menu, go to Meta > Tools > Oculus Platform Tool.
Depending on the target build you’ve set from the Build Settings window, the Target Oculus Platform automatically sets the target device to Quest or to Link PC-VR.
In Oculus Application ID and Oculus App Token, enter the ID and token that are available on the API page of the Meta Quest Developer Dashboard.
Note: You must use an admin account to view the app secret. In case you’re not an admin, go to the Meta Quest Developer Dashboard and verify the admin accounts listed in the Members tab.
In Release Channel List, enter the release channel name. See Oculus Platform Command Line Utility for valid release channel names.
In Release Note, enter the release notes for the version.
In Build APK File Path, select the .APK file.
In Debug Symbols Directory, select the debug symbol directory path to symbolicate the Android crash and analyze the crash logs on the Crash Analytics dashboard. The tool defaults to the directory path of the libil2cpp.sym.so file, which is the default symbol file for projects built using the IL2CPP scripting backend. If you’re using IL2CPP scripting backend to build your project, you don’t need to take any action unless you want to use a different symbol file or choose not to upload the file.
For projects that were built using the Mono scripting backend, select the directory path C:\Program Files\Unity\Hub\Editor\<version>\Editor\Data\PlaybackEngines\AndroidPlayer\Variations\mono\Release\Symbols\armeabi-v7a to upload the libunity.sym.so symbol file. Should you choose not to upload the symbol file, click the X icon to clear the file path.
To upload debug symbols to an existing build, select Upload Debug Symbols Only check box, and in the Build ID box, enter the build ID. You can get the build ID from the Meta Quest Developer Dashboard in the Distribution > Release Channel tab.
Expand Optional Commands > Expansion Files to add additional files such as OBB and asset files. Do the following:
- Click Choose to select the OBB file. The OBB file plays a role of extending the overall size of your app. Meta Quest supports up to 4 GB OBB file.
- Click Choose to locate the folder containing the asset files. Meta Quest supports up to 2 GB asset files that can be used as DLC.
Click Upload.

Upload Link PC-VR builds

On the menu, go to File > Build Settings > Build to compile the build.
After the build is compiled, on the menu, go to Meta > Tools > Oculus Platform Tool.
Depending on the target build you’ve set from the Build Settings window, the Target Oculus Platform automatically sets the target device to Quest or to Rift (Link PC-VR).
In Oculus Application ID and Oculus App Token, enter the ID and token that are available on the API page of the Meta Quest Developer Dashboard. To retrieve the app ID and token, log in to the dashboard, find the app from the list of apps under your organization, go to the Getting Started API page, and copy the app ID and token. You must use an admin account to view the app secret. In case you’re not an admin, go to Settings and verify the admin accounts on the Members page.
In Release Channel List, enter the release channel name. See Oculus Platform Command Line Utility for valid release channel names.
In Release Note, enter the release notes for the version.
In Rift Build Directory, select the directory containing the build files.
In Version Number, enter the build version number.
In Launch File Path, select the .EXE file.
Expand Optional Commands and do the following:
- In Launch Parameters, enter any arguments passed to the launcher file.
- Select Firewall Exception to enable Windows firewall exception.
- In the Gamepad Emulation list, select the type of gamepad emulation used by the Meta Touch Controllers.
- Under 2D, in 2D Launch File, select the .EXE file to launch the app in 2D mode, and in 2D Launch Parameters, enter any arguments passed to the launcher file.
- Under Expansion Files, in Language Pack Directory, select the directory containing the language pack, and in Assets Directory, select the directory containing the DLCs.
Click Upload.