-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Did not get a valid Oculus ID #1
Comments
If the oculus id is 0, then that generally means entitlements were not granted to the account the headset is on. Could you validate the following things?
If you have already tried (2) and still run into the same issue, an alternative approach would be to go to Also once entitlements are granted, you can freely sideload the same APKs and should not receive the same issue. |
Thank you for your response. I have already validated both aspects. The OculusPlatformSettings.asset file is correctly configured with the correct Oculus Store ID. Additionally, I have downloaded the app from the store, not as an APK. I have tested by publishing in the production channel and also in other channels, inviting the account, and it allows me to download it. However, upon entering, the same error persists. |
Hello, I'm facing the same issue and also tried the provided steps. |
Having the exact same issue. HAs anyone found a solution, or ist this sample working for anybody? I ran into the same oculus id not valid issue on all platforms |
Yes, the sample is working! We built a working colocated beer pong application based on the Netcode for GameObjects example. |
In short: If you are using the Oculus Platform SDK, you first need permission to access certain user information. In this case, the example is trying to access the user's ID, but it is not authorized to do so. |
Oh, can you explain step by step how to give acces yo the useer's ID in the app? Thanks |
To get access to the user IDs in the App do the following
|
Thank you for your response! After following the steps, indeed, we can now access the player's ID without that error, and I can see an axis marker in the center of the app. However, when opening the application on two different devices, both see a different axis marker, even though both are on the same Wi-Fi on different Meta accounts. I will be doing more tests and checking if all the logcat debugs are correct, but for the moment I haven't seen anything. |
if i not business member |
I consistently encounter the error 'NGOSampleFlowBootstrapper: Did not get a valid Oculus ID' due to the ID being set to 0. However, my application is meticulously configured for both building and publishing in the Meta Store. Despite following the correct procedures, the Oculus ID remains 0, preventing successful execution. Any assistance in resolving this persistent issue would be greatly appreciated.
The text was updated successfully, but these errors were encountered: