04-23-2017 11:14 PM - edited 04-23-2017 11:15 PM
We're having trouble testing the viveport leaderboards. We've plugged it into the Unity build with the viveport id etc..
But we don't know how to launch a build that connects to it. We keep getting error "you are not the owner" and error code 5001 which indicates invalid account id.
Is there a way to launch a developer build? Or is there some other way to test this? The build is not in review yet.
Solved! Go to Solution.
04-26-2017 07:33 AMSolution
Assuming you followed the steps here regarding obtaining your Viveport/App ID:
Please be sure not to login into the Viveport login and developer console login with different accounts
Let us know if you're still having issues.
3 weeks ago - last edited 3 weeks ago by VibrantNebula
3 weeks ago
Sorry for late response.
Actually, if you are testing in the published build, you can ask us a redeem code for tester to buy your content and do the test.
3 weeks ago
If you need the Vive coin to invite your staff to purchase the content and test the leaderboard SDK, please tell me how much is for your content and how many staff you plan to run the test.
2 weeks ago - last edited 2 weeks ago
We aren't testing in a published build, as we didn't want to publish until we'd tested everything... So I guess the advice is publish, and then test it?
Edit: It is possible I am being completely dense here, but my understanding is: Viveport M has no beta channel, only production, and no way to grant entitlement to accounts other than the main app account while in development, so my understanding right now, is that you have to submit to production, get through your submission process, and then test your application using the public build downloaded from the store? Hence your offer of some free keys?
Somewhat related, it is also apparently not possible to test our integration of your DRM SDK, as it 100% fails the licence check even on the account that created the app (the leaderboards worked with this account but no other), and apparently we need a "test ID" to test it, but this does not exist on the dashboard for Viveport M. Hoping someone can point out if/where I am going wrong, or confirm there simply isn't a supported way of testing any of this outside of production.