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?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.
Test User account revoking IAP is missing? Where did it go?
With a Test User account, we had the ability revoke IAP allowing us to properly test out the feature for our projects. This feature has since disappeared and for testing purpose, it feels like I need to reset my device with a new account if I want to test a fail state and a pass state. Is there a workaround to this?
Build Fails for non-developers added to Release Channels
Hi There, We have just started running into a problem with adding new users to our release channels for a game that is in development. Through the developer dashboard we can add oculus account usernames appropriately, and our title will appear as downloadable when searched for through Oculus home. However, the download and installation fails when attempting to actually run it. The way that we have worked around this issue internally is to add the oculus account as a developer in our organization's member page, however we can't really do this when attempting to allow external partners and players. Has anyone else come across this issue with release channels? Is there a way to ensure a user can have access to a release channel for a game that is in development that does not involve adding them as a developer? Thanks very much! -Nate S. QA Lead, Harmonix
