Add 'deploy to oculus hub' feature
Dylan-Whiteford opened this issue · 4 comments
Context
- I am making a VR solution for the oculus quest two.
- I've set up a github repo to work from
- Its a unity project
- I'm using git LFS
- I'm using game-ci to build my project
Suggested solution
You have a means to deploy builds to various app stores(microsoft, steam, etc...) . So far I haven't found a way to deploy to the oculus quest developer hub. I was wondering/hoping this would be possible?
Considered alternatives
I manually download the build file and upload it myself to the oculus developer hub
Additional details
the oculus developer hub is a platform for publishing oculus apps. It has its own process for verifying APK builds.
the quest two only make use of android APK s. You need to include a .keystore file in the 'player' settings when you make a build
Hey Dylan,
Thank you for your suggestion.
I'm moving this issue to our documentation repo.
It doesn't look like there is an action for oculus developer hub yet. So that's definitely a valid use-case for creating one. We'd be happy to maintain such an action together with our community, however we're dependent on that same community for creating something initially.
For building the APK and dealing with the keystore, you should generally be able to follow at least most of the Google Play flow in our documentation.
Of note - it seems the OVR platform Util does not have a Linux build as of yet (just macOS and a PC .exe) https://communityforums.atmeta.com/t5/General-Development/ovr-platform-util-on-Linux/td-p/965220
Interestingly this works - here's a one-liner to use docker/wine to run the ovr-platform-util exe to upload an apk you have in the same folder:
-
Install Docker
-
Put your apk and ovr-platform-util.exe in your current folder
-
Run ovr-platform-util.exe in wine in a docker container (configure for your app and exe/apk path)
docker run -t -v .:/files_to_use -w /workspace jmschrack/winehq:stable wine /files_to_use/ovr-platform-util.exe upload-quest-build --app_id YOUR_APP_ID --app_secret YOUR_APP_SECRET --apk /files_to_use/YOUR_LOCAL_FILENAME.apk --channel alpha --notes "This is an alpha build"
You need to include a .keystore file in the 'player' settings when you make a build
This is now supported at build time by base64 encoding your keystore file into an environment variable, for a GitLab example see: https://game.ci/docs/gitlab/deployment/android/ and the GitLab example repo's before_script.sh