Skip to main content
New Participant
October 2, 2018

The user isn't signed in

When running a dev build of my app built with Unity on the GO, I get the following error through the logs after the platform is initialized:
The user isn't signed in or their account state wasn't in a recoverable state.
I am signed in on the device, but not sure how to sign out to refresh the token if that's required, without factory resetting.
Does anyone how to fix this?

This also causes the following error when attempting to get user data:
 {"error":{"message":"Invalid OAuth 2.0 Access Token","type":"OCApiException","code":190,"error_data":[],"fbtrace_id":"AdktSl4ek+I"}}

This topic has been closed for replies.

7 replies

New Participant
April 15, 2019
I have this exact same issue.  :(
April 16, 2019
The only way to change accounts associated with the headset, is to factory reset - unfortunately =/
JeffNik
Honored Contributor
April 17, 2019
Are you guys using the "Build and Run" button in Unity to push the app to the Go, and that's when you get this error? I have read in web resources, but haven't tested it yet, that to test platform logged-in-user functionality on the actual device - you have to upload your test build to Oculus, add yourself as a test user, and download the app through the Go's interface - "sideloading" the app to the device from Unity wont let your Oculus account log in.



Up and Coming
July 9, 2020
Did you ever find a solution to this? I am getting this exact same error message when trying to retrieve player high scores from alpha and store channels.
New Participant
July 9, 2020
Hey @CNevan, sorry no I never found the solution to this
Up and Coming
July 9, 2020
That's ok, thanks for your response!
February 5, 2022

Have you ever found the way to fix it yet