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/
Ah, looks like Get is used for collecting info on users other than your own, whereas LoggedInUser is only for your own user account on the headset. Definitely looks like you're following the verification process exactly as outlined in the documentation. The invalid userid requests all falling into the same number range is definitely suspicious...