Welcome to the Oculus Developer Forums!
Your participation on the forum is subject to the Oculus Code of Conduct.
In general, please be respectful and kind. If you violate the Oculus Code of Conduct, your access to the developer forums may be revoked at the discretion of Oculus staff.
Your participation on the forum is subject to the Oculus Code of Conduct.
In general, please be respectful and kind. If you violate the Oculus Code of Conduct, your access to the developer forums may be revoked at the discretion of Oculus staff.
Using Test Users to test IAP appears to be impossible at the moment
Atoramos
Posts: 19 NerveGear
Edit: I hadn't realized the 'Answers' subforum was for people seeking general answers, and thought it was a problem presumed answered. Either way, I believe this to be a problem for the SDK Development subforum, and is a showstopper for us:
https://forums.oculus.com/developer/discussion/43482/accepting-release-channel-invitation-on-a-test-account#latest
In a nutshell, when you create a test user a subaddressed e-mail is used (which makes sense as you want to prevent multiple users being created).
However, when you go to add users to a release channel you need to accept an e-mail invitation. This invitation goes to the subaddressed e-mail, which does not exist. It is impossible to change e-mails on this subaddressed account. Thus, as far as we can tell, it is impossible to accept this invitation and actually test any release channel from a test account. The fix seems simple to me, just don't require this e-mail sign-off from test accounts. In the meantime, is there any way around this so we can use a Test User (and thus the Test Payment Info) for our IAP?
https://forums.oculus.com/developer/discussion/43482/accepting-release-channel-invitation-on-a-test-account#latest
In a nutshell, when you create a test user a subaddressed e-mail is used (which makes sense as you want to prevent multiple users being created).
However, when you go to add users to a release channel you need to accept an e-mail invitation. This invitation goes to the subaddressed e-mail, which does not exist. It is impossible to change e-mails on this subaddressed account. Thus, as far as we can tell, it is impossible to accept this invitation and actually test any release channel from a test account. The fix seems simple to me, just don't require this e-mail sign-off from test accounts. In the meantime, is there any way around this so we can use a Test User (and thus the Test Payment Info) for our IAP?
0
Categories
- 16.4K All Categories
- 839 General Development
- 171 AMA
- 1.3K Answers
- 131 Developer Dashboard
- 468 Store Submissions
- 1K Oculus Quest Development
- 3.9K Oculus Rift S/Rift Development
- 1.9K Oculus Go Development
- 16 OpenXR Development
- 3 Accessibility Development
- 4.1K Unity Development
- 1.1K Unreal Development
- 411 Platform SDK Development
- 358 Audio SDK Development
- 293 Avatars / Social SDK Development
- 17 360 Capture SDK Development
- 32 Developer Tool Feedback
- 402 Game Design
- 512 Collaboration
Comments
I am currently looking into this and will advise you on what information I find that is applicable to your situation.
Having an issue with our platform, services, or integrations?
Try using our new bug tool to report this and receive emailed updates as we proceed to address it internally.
1) Create Test Account & copy the email address.
2) Add the Test Account to the Alpha channel for our build
3) Open the Oculus Store on the desired PC or Phone and log into the test account. Scroll to the bottom of the Store page to the 'preview' apps section, and click the 'FREE' or 'BUY' button to add it to your library.
On Android:
- You need to create a build that uses the APP ID and apk package name that you submitted to the store. You have to have submitted a valid build before the platform SDK will initialize. Once you've uploaded your first build, you can just manually adb push builds to the phone and have them work.
On PC:
- While you can use some of the SDK calls in the Unity Editor, the IAP store does not appear to work unless you create a PC build.
- In addition, I usually get errors using builds that arn't in the Oculus download folder unless I set the following registry key:
reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Oculus VR, LLC\Oculus" /v AllowDevSideloaded /t REG_DWORD /d 1 /f
When you create a test account you have to assign a password and pin to it.
When you add the test user to a release channel they are automatically added to the Subscribed Users list. There is no longer a need to confirm the email of test users.
Having an issue with our platform, services, or integrations?
Try using our new bug tool to report this and receive emailed updates as we proceed to address it internally.