Deploy builds to Quest

This tutorial shows you how to build and deploy a sample WVS project to your Meta Quest developer account all from the WVS Web Client. Once you complete this tutorial, you can see your deployed app on your Quest headset. The objectives of this tutorial are as follows:

flowchart LR; id1[Create a Quest app] --> id2[Fork a sample project on WVS]; id2 --> id3[Point your WVS project to your Quest app]; id3 --> id4[Build and deploy your project to your Quest app]; id4 --> id5[See your app on your Quest headset];

Prerequisites

You must have an Meta Quest developer account.

Create a Quest app

You can deploy your WVS project builds directly to your Quest apps. Each Quest app has a unique App ID and an App secret, which is a token that’s used by applications to make Quest API requests. You must configure your WVS project with the App ID and App secret of your Quest app to automate the deployment of builds to your Quest app.

Additionally, your build for this tutorial deploys to Quest as a pre-release Alpha. Only invited users can find pre-release versions of Quest apps, so you must invite any users, including yourself, that you want to use your app in order for them to see it on their Quest headsets.

Create a new app

  1. Sign in to Meta Quest Developer Center and click My apps.
  2. Click Create new app.
  3. In the popup window, enter a name for your app and select Quest (app lab).

  4. Click Create.

    Once your app is created, you are taken to the Overview page of your new app in the App manager.

Get your app’s App ID and App secret

  1. In the App manager navigation page, select API.
  2. Copy and save the App ID and App secret. We use these values in later steps to point your WVS project to your Quest app.

Invite users to use your app

  1. In the App manager navigation panel, select Distribution > Release channels.
  2. Click Alpha and select the Users tab.
  3. Click Add users and enter the Quest account emails of the users that you want to invite to use your app, including yourself.

Fork a sample project on WVS

For this tutorial, we fork the sample project Ue5VrStarterQuest, which you can build and deploy to your Quest app.

  1. Go to the Ue5VRStartQuest project home page.

  2. Click Fork and configure your project as follows:
    • Project name: Enter a name for your project or keep the original name.
    • Project URL: Select the namespace for your project. It could be your personal namespace or the namespace of any groups that you own. For the purposes of this tutorial, we recommend selecting your personal namespace.
    • Project slug: Enter a URL-friendly name for your project.
    • Visibility level: For the purposes of this tutorial, we recommend using private visibility.
  3. Click Fork project.

Now you have your own copy of the Ue5VrStarterQuest sample project.

Point your WVS project to your Quest app

To enable your forked project to deploy builds to your Quest app, your project must have the App ID of your app and the credentials for making Quest API calls.

  1. In the WVS Web Client, open your forked copy of Ue5VrStarterQuest.

  2. In the navigation panel, select Project settings > CI/CD.

    Note: If you don’t see CI/CD, you need to select Show advanced developer tooling in your WVS profile preferences page.

  3. Expand the **Variables **section.
  4. Click Add variable and configure your Quest app’s App ID:
    • Key: WVSUSR_QUEST_APPID.
    • Value: Enter the App ID of your Quest app.
    • Type: Variable.
    • Environment Scope: All (default).
    • Protected variable: Unselect.
    • Masked variable: Select.
  5. Click Add variable.
  6. Click Add variable again and configure your Quest app’s App secret:
    • Key: WVSUSR_QUEST_APPSECRET.
    • Value: Enter the App secret of your Quest app.
    • Type: Variable.
    • Environment Scope: All (default).
    • Protected variable: Unselect.
    • Masked variable: Select.
  7. Click Add variable.

Build and deploy your project to your Quest app

This project takes around 30 minutes to build.

  1. In the WVS Web Client, open your forked copy of Ue5VrStarterQuest.
  2. In the navigation panel, select Version control > Files.
  3. Click the Readme.md file and click Edit.
  4. Make any change to the file and click Commit changes.
  5. In the navigation panel, select Flows > Pipelines and click Run pipeline.

  6. Click Run pipeline without making any configuration changes.

    You are taken to the pipeline details page where you can see the progress of each job.

Once all jobs successfully complete, you are ready to see your Quest app on your Quest headset.

Tip: You can see your builds in Output > Builds.

See your app on your Quest headset

You can find your app in your app library with the App lab label. If you don’t see your app in your app library, try searching for it in the Store. Once you’ve located your app, you can install it and use it.

You can also make edits in your WVS project and build and deploy it again to Quest. In this case, the next time you open your app, you are prompted that a new version of the app is available and you can update to the newer version.