Channel users not getting invitations, unable to test app
We have an unpublished Quest (App Lab) app which we're trying to share with some testers. We added their emails to the RC channel, but they never received an email invite. Any email I add immediately goes to Subscribed Users instead of Pending, but they are unable to find the app in the store. We actually tried this with 2 different apps and had the same result. The only users who this does work for are those that are members of our org on the dashboard (the developers). They don't receive the email, but are able to see the app in their library. Am I doing something wrong, or are invites broken?
Hounded by VRC.Quest.Functional.3 out of compliance checks
We're currently plagued by VRC.Quest.Functional.3 requirements for our Job Interview Simulator application on the Meta Store. We've received a request for action related to this VRC twice. Each time we've resolved the violation according to an email we received. We have provided login details to satisfy the VRC requirements, as directed. We've also seen the account being accessed. It's hard to clarify any information on the requirements for VRC.Quest.Functional.3. Can somebody from the team help us identify where we are failing our test with a little more information? I assume this is part of an automated test.
Testing Shared Spatial Anchors during dev
Hello everyone, I am building an app that requires shared spatial anchors, thus it is a multiplayer app. So I have two questions: 1- Quest development requires using Quest Link when trying the app in Unity, which is fine, but when I want to test in multiplayer, I often use ParallelSync and open two Unity editors. But it seems abit difficult to do the same now on the same PC connecting 2 Quest devices. Any suggestion around this? 2- Sharing spatial anchors requires App ID, which seems to only work after you build the app and upload to App Lab, this will be incredibly time consuming, is there a way to use and share spatial anchors using Unity Editor and Meta Quest Link without building every time? Thanks alot everyone.
Cannot upload Applab build - OCULUS_PLATFORM__APK_PACKAGE_NAME_ALREADY_IN_USE
Hello! I am trying to upload my game to applab for submission and testing, but I keep getting the same error OCULUS_PLATFORM__APK_PACKAGE_NAME_ALREADY_IN_USE. I've already tried re-creating the application, re-building the game. But nothing worked. Can anyone help me?No tests initiated for new App Lab build - prevents app from updating for everyone
I uploaded a new build to Oculus Quest App Lab (alpha release channel). Usually, automated testing runs immediately and finishes within a few minutes. Then, the app updates for everyone. However, I am experiencing an issue where no tests are initiated at all. Under "Test Results" it says "No test runs were found to be associated with this build." And under "Build History", it is just blank under "Test Results". This fully prevents the app from pushing to everyone. Because no tests were run, it is stuck on the previous version and the app does not update.
AutoDriver - Our E2E testing is no longer working
We were using AutoDriver, found here: https://developer.oculus.com/documentation/unity/ts-autodriver/ This no longer seems to work. The command that causes issues is: "adb shell debug.oculus.autoDriverApp". This will always return: "/system/bin/sh: debug.oculus.autoDriverApp: inaccessible or not found". This has seriously affected our testing, as we used this system for our E2E testing. If anyone has information on this issue, good or bad, please reach out. My team is small and heavily relied on this system.Alpha Channel Apps not showing on tester devices
Have been navigating this issue for quite some time wanted to know if other devs are encountering it as well. - Alpha Channel invites to testers sent, testers never receive email invite - Even if testers receive invites and accept them, preview app fails to show up on their devices - Adding to developer org and then subscribing testers works sometimes, sometimes does not work There seems to be a lot of inconsistency with these services, or am I the only one still facing this. Perhaps I am missing out on something. I even went ahead and ensured dev mode is enabled on every device (in the case that alpha channel builds require dev mode although I doubt they do). Any Insight would be appreciated!
