When we authenticate using OAuth2 there’s a bug that can be reproduced the following way.
Step 1) Authenticate and authorize your app on device 1, iPhone for instance.
Step 2) Commit at least one data point using this device.
Step 3) Authenticate and authorize your app on device 2, iPad for instance
Step 4) Commit at least one data point using the second device
Step 5) Go back to device one and you will notice that its auth_token is no longer valid.
Sounds like we’ve maybe got a uniqueness constraint on the User to Client authorizations. I’ve only implemented things on our API where there’s only one instance of the client (e.g. Zapier). I’ll take a look at this. When you authorize on the second device do you get the prompt to authorize your application a second time? Or do we do the passthrough (where we skip and redirect back to your app since the user’s already authorized the application).
Bethany
I can authorize the second device but it cancels the first authorization.
I don’t know if you do the passthrough or not, I don’t remember, I’ll try to reproduce it later.
It does a passthrough
I think this bug is still open