... | ... | @@ -2,7 +2,7 @@ |
|
|
Before we get started, here is a list of variables you will need to deploy Hello-World to your Quest.
|
|
|
|Variables |
|
|
|
|--- |
|
|
|
|WVSUSR_Quest_APPID |
|
|
|
|WVSUSR_QUEST_APPID |
|
|
|
|WVSUSR_QUEST_APPSECRET |
|
|
|
|WVSUSR_ANDROID_KEY_ALIAS_NAME |
|
|
|
|WVSUSR_ANDROID_KEY_ALIAS_PASS |
|
... | ... | @@ -18,7 +18,7 @@ Select **My Apps** to get started. |
|
|
|
|
|
![newapp](https://wvs.io/wvs-project-examples/hello-world-unity-vr-quest/-/raw/main/rdmeimg/create_new_app_oculus.png)
|
|
|
|
|
|
3. Click on the app you just created from the list of apps.
|
|
|
3. Click on the app you just created from the list of apps in the [Oculus Developer Center](https://developer.oculus.com/) .
|
|
|
|
|
|
4. On the left-hand side, select **API**.
|
|
|
- In the center of the page, locate **APP ID** and save this number for later.
|
... | ... | @@ -26,12 +26,12 @@ Select **My Apps** to get started. |
|
|
|
|
|
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).
|
|
|
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
|
|
|
But to help you get started, you can clone using the Desktop Client.
|
|
|
- In your WVS Desktop Client, select **Remote Projects** from the tab on the left-hand side. The project you just forked should
|
|
|
appear on the list. Click Clone. Your Project should now be in the **My Projects** tab on the left.
|
|
|
|
|
|
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
|
|
|
- In the WVS Desktop Client, you will start a changelist by selecting the **New Changelist** tab on
|
|
|
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
|
... | ... | @@ -39,9 +39,9 @@ But you can clone using the Desktop Client. |
|
|
- You can ignore the optional file tree for locking files since we're just editing the project
|
|
|
settings.
|
|
|
- Any files that got changed will automatically show up in the appropriate section under
|
|
|
Modified Files in the desktop client. We won't commit any changes just yet.
|
|
|
Modified Files in the desktop client. **We won't commit any changes just yet.**
|
|
|
|
|
|
7. Since your project is local, we can make some changes to the project settings. Open the project up in Unity. Here is a list of the variables you'll need to store in this step.
|
|
|
7. Since your project is local, we can make some changes to the project settings. Open the project in Unity. Here is a list of the variables you'll need to store in this step.
|
|
|
|
|
|
|Variables |
|
|
|
|--- |
|
... | ... | @@ -62,30 +62,36 @@ But you can clone using the Desktop Client. |
|
|
`openssl base64 -A -in <yourKeystore>.keystore`
|
|
|
- Copy the output (a long string) and save it for the following variable.
|
|
|
**WVSUSR_ANDROID_KEYSTORE_BASE64**
|
|
|
- Now you are ready to push your changes to the remote repository, you will need to fill in
|
|
|
the Changelist Notes section with a brief description of your changes.
|
|
|
- Finally, press the COMMIT CHANGELIST button and follow the instructions to push.
|
|
|
|
|
|
9. Grab your login information for your Unity Account and save the information with the others.
|
|
|
|
|
|
|Variables | Description |
|
|
|
|--- |--- |
|
|
|
|WVSUSR_UNITY_PASS | Your Unity Password |
|
|
|
|WVSUSR_UNITY_USER | Your Unity Username |
|
|
|
|
|
|
9. With all the variables that were collected in the previous steps, you'll enter them into your project variables in the WVS web.
|
|
|
- In the WVS web app, go to your project, scroll to the bottom, and in the left-hand nav, select
|
|
|
10. With all the variables that were collected in the previous steps, you'll enter them into your project variables in the WVS web.
|
|
|
- In the WVS web app, go to **My Project >> View All Projects** and select your project. Scroll to the bottom, and in the left-hand nav, select
|
|
|
**Project Settings>> CI/CD**. Locate **Variables** and expand the section.
|
|
|
![var](https://wvs.io/wvs-project-examples/hello-world-unity-vr-quest/-/raw/main/rdmeimg/wvs1.png)
|
|
|
|
|
|
- Click the **Add Variable** button and add all your variables from the list, one at a time.
|
|
|
|
|
|
9. Once this is set up, you can enable the flows in the desktop client by doing the following.
|
|
|
11. 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.**
|
|
|
- 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 successfully.
|
|
|
- Now you are ready to push your changes to the remote repository, you will need to fill in
|
|
|
the Changelist Notes section with a brief description of your changes.
|
|
|
- Finally, press the COMMIT CHANGELIST button and follow the instructions to push.
|
|
|
12. Once the build completes, you can go to your [Oculus Developer Account](https://developer.oculus.com) and check that your build was deployed successfully.
|
|
|
- Go to your app and select Overview from the left-hand nav. You will see your build
|
|
|
information there once it is deployed successfully.
|
|
|
- Your App should show up under APP LAB, and if it doesn't show automatically, you will
|
... | ... | |