Issue 1: The error message we were returning ("Your device's clock is off...") was incorrect due to a bug in Splitwise's server code. That will be fixed shortly in a separate PR.
Issue 2: Our instructions weren't clear enough about how to find the bearer token correctly. When using our sample code to obtain a Bearer token, you should NOT copy the token from the URL – that token is just an authorization code, and not an actual Bearer token. I've updated the instructions for ruby--oauth2 to print the Bearer token more clearly to the console, and added comments to help guide future developers.
Closes #7.
Issue 1: The error message we were returning ("Your device's clock is off...") was incorrect due to a bug in Splitwise's server code. That will be fixed shortly in a separate PR.
Issue 2: Our instructions weren't clear enough about how to find the bearer token correctly. When using our sample code to obtain a Bearer token, you should NOT copy the token from the URL – that token is just an authorization code, and not an actual Bearer token. I've updated the instructions for
ruby--oauth2to print the Bearer token more clearly to the console, and added comments to help guide future developers.