Forum Discussion
Solved
invalid_request for some nonces / user_id when posting to user_nonce_validate
I’m following the user verification flow from meta here: https://developer.oculus.com/documentation/native/ps-ownership/#integrate-user-verification … in order to validate the identity (user...
Turns out this was a JSON parsing issue. For other devs that run into this, Meta's documentation suggests using a ulong for user ID's, but JSON serializing for S2S Rest API's would often corrupt the end of the ID. Hence, Oculus server's will return the verify request as "invalid" since it was missing the entirety of the ID. We solved this by serializing the ID as a string, and passed that via S2S instead, which reduced most of the "invalid" requests. More on this here:
https://jsoneditoronline.org/indepth/parse/why-does-json-parse-corrupt-large-numbers/
Wondering if there is a difference between using ovr_User_Get() vs. ovr_User_GetLoggedInUser() when it comes to verifying user ids with GetUserProof? The user verification documentation uses LoggedInUser but the v51 SDK Reference says to use Get, so I'm not sure why the redundancy or the difference between the two methods?