... | ... | @@ -11,7 +11,6 @@ To Deploy Hello-World to your Quest, we will need the following variables. Detai |
|
|
|WVSUSR_ANDROID_KEYSTORE_BASE64 |
|
|
|
|WVSUSR_UNITY_PASS |
|
|
|
|WVSUSR_UNITY_SERIAL |
|
|
|
|WVSUSR_OCULUS_TOKEN |
|
|
|
|
|
|
1. Go to [Oculus Developer Center](https://developer.oculus.com/) and log in with your credentials.
|
|
|
Select **My Apps** to get started.
|
... | ... | @@ -29,11 +28,15 @@ Select **My Apps** to get started. |
|
|
- Locate **App Secret** and copy the secret and save this for later.
|
|
|
|
|
|
5. Now, we are going to move into the project on unity. To clone your project to your local
|
|
|
directory, you can use the Desktop Client, the CLI, or the web app. Detailed steps can be found on our [Docs Site](https://docs.wvs.io/wiki/Projects/Clone/Clone-Project-in-Web-App.html)
|
|
|
directory, you can use the Desktop Client, the CLI, or the web app. Detailed steps can be found on our [Docs Site](https://docs.wvs.io/wiki/Projects/Clone/Clone-Project-in-Web-App.html).
|
|
|
But you can clone using the Desktop Client.
|
|
|
- Select **Remote Projects** from the tab on the left-hand side. The project you just forked should
|
|
|
appear in the list. Click Clone. Your Project should now be in the **My Projects** tab on the left.
|
|
|
|
|
|
6. Once you have your project locally, open up the **WVS Desktop Client**.
|
|
|
6. Once you have your project locally, you can make some changes to the project.
|
|
|
- In the Desktop Client, you will start a changelist by selecting the **New Changelist** tab on
|
|
|
the left.
|
|
|
the left. We want to start a changelist because we will be making some changes to the project
|
|
|
settings.
|
|
|
- You will need to enter a name for your new changelist in the text field that has the text
|
|
|
**Enter New Changelist Name**.
|
|
|
- You can ignore the optional file tree for locking files since we're just editing the project
|
... | ... | @@ -73,10 +76,23 @@ directory, you can use the Desktop Client, the CLI, or the web app. Detailed ste |
|
|
|
|
|
- Click the **Add Variable** button and add your variables, one at a time.
|
|
|
|
|
|
9. Once this is set up, you can trigger a build by making a small change in the readme and adding a commit message (**-execute_quest**) to trigger the build.
|
|
|
9. Once this is set up, you can enable the flows in the desktop client by doing the following.
|
|
|
- The WVS Desktop client uses a simple interface to manage a single active changelist at a time. A
|
|
|
changelist is a list of changes that you will apply to your repository.
|
|
|
- First, you need to select the **New Changelist** tab on the left
|
|
|
- You will need to enter a name for your new changelist in the text field that has the text **Enter
|
|
|
New Changelist Name**
|
|
|
- You can ignore the optional file tree for locking files since we're updating the flows.
|
|
|
- At this point, you may change the flows in your repository, and they will automatically show up in
|
|
|
the appropriate section under **Modified Files.**
|
|
|
- The JSON files to change are in `.wvs/flows`
|
|
|
- Open the first file, and you will change the second line `"Enabled": false` to `true`.
|
|
|
|
|
|
10. Once the build completes, you can go to your [Oculus Developer Account](https://developer.oculus.com) and check that your build was deployed.
|
|
|
- Go to your app and select Overview from the left-hand nav. You will see your build
|
|
|
information there once it is deployed successfully.
|
|
|
- To view it on your Oculus, you can search for the app by using the exact project name
|
|
|
**Hello-World** |
|
|
- Your App should show up under APP LAB and if it doesn't show automatically, you will have to
|
|
|
search on your device by using the exact project name **Hello-World**.
|
|
|
|
|
|
### Troubleshooting
|
|
|
For additional support, please reach out to us on our Discord or by Email. |