UPDATE #3
Since I’m able have users login to my app (normal username and PW), then click a button to “Connect to Quickbooks” which would display QB data via Oauth, I wanted to test and verify before moving to the next step.
This is where I ran into issues.
Sometimes Oauth will redirect back to my application perfectly and QB data will display in my app fine. Other time’s I run into these issues:
- While on mobile I’ve seen error code 400 “redirect ID invalid”. This seems to happen occasionally, I can just refresh and try again and the issue corrects itself.
- I get an error about the email already on another account for this email. Occasionally I can fix this by trying to connect QuickBooks multiple times, which creates the same RealmID and adds it to the URL (?realmId=xxxxxxxx&?realmId=xxxxxxxx&?realmId=xxxxxxxx&?realmId=xxxxxxxx&). Somehow this eventually works. There’s two known issues which might help explain this:
-
You can’t log into an app with a normal username and password and then press a button to authorize a login via another service. Bubble was built to log you out and then log you in under the quickbooks account credentials. There’s a couple threads on this already. Here’s one thread and here’s the other. You’ll see here that this is NOT the case anymore. Bubble will allow you to login via username and PW and then click a button to Oauth another service all while still logged in. (I’m not sure if this is confirmed - I occasionally get logged out).
-
It seems you can’t Oauth multiple bubble users to one quickbooks account. Here’s details on that.
I’ll continue to explore the issues on 1 and 2 above. I need to fix, or fully understand, both items before building workflows with QB data. Depending on how things work out, it might be a deal breaker for my app.