Forum Discussion

flavobarth's avatar
flavobarth
Explorer
3 years ago
Solved

Nothing happens with Entitlements.IsUserEntitledToApplication()

Absolutely nothing happens when I call Entitlements.IsUserEntitledToApplication(). I'm trying to test this in Unity editor standalone platform. The callback is never executed and no exceptions are th...
  • flavobarth's avatar
    flavobarth
    3 years ago

    Thanks, JeffNik. I did add my test user accounts to the Alpha Channel of the app, but that didn't work either.

    I have found a workaround though. Apparently if I uncheck "Use Standalone Platform" in Oculus > Platform > Edit Settings (so that the account logged in the Windows Oculus App is used instead of the test user I have informed), the entitlement check works!

    I'll use this for now, although it is still weird that I can't use the standalone platform in this specific app, considering that our other apps with the same settings work. Hopefully you're right and they are changing some API stuff, and eventually things will sort themselves out.

flavobarth's avatar
flavobarth
Explorer
3 years ago

Thanks, JeffNik. I did add my test user accounts to the Alpha Channel of the app, but that didn't work either.

I have found a workaround though. Apparently if I uncheck "Use Standalone Platform" in Oculus > Platform > Edit Settings (so that the account logged in the Windows Oculus App is used instead of the test user I have informed), the entitlement check works!

I'll use this for now, although it is still weird that I can't use the standalone platform in this specific app, considering that our other apps with the same settings work. Hopefully you're right and they are changing some API stuff, and eventually things will sort themselves out.

Extrys's avatar
Extrys
Explorer
2 years ago

It was happening to me, until i just clicked on the "Clear credentials" button and typed in the credentials again, sometime seems that with oculus sdk updates or unity updates, or any other kind of change, can affect the scriptable wich "thinks" you still correctly logged, but no, also other cause is when you change your account credentials, in unity the old credentials doesnt get updated and neither does the scriptable to say "hey your credentials are incorrect now" so internally when trying to connect to oculus it cant even complete the autentication because cant even login correctly