I don’t know when this happened, but it appears that when generating a user token using the Log In user backend workflow with user email and password, the token’s format has changed from “1714423022372x495316453461721000” to “bus|1532046738452x794314432119549562|1714423022372x49531645156984672”.
This means that any API workflow using the token as authentication will fail to authenticate. Likely because the internal bubble APIs are still expecting a 32 character Bearer token.
I can confirm that 2 of my apps no longer can create things in the database using a generated user token.
To help promote this thread / chime in (I know you saw my post already so sharing for others), yes - this change has been in effect for roughly a month and it is indeed breaking Bubble integrations. It has broken Bask (details here). Am really curious to know who else is impacted / the scale of the problem.
**Edit - I could be wrong but I don’t believe Bubble reviews this channel for official bug reports. If you haven’t already @swms, do report this either:
Checked with the team. Nothing expects a 32 char token.
The best thing to do is to submit a ticket to support. They can help with connecting you to the right resources and, if there is anything engineering missed, they can also surface it to them
@swms did you ever manage to figure out what broke for you? It sounds like the returned token format is different but it should still work. Curious if there’s a corner case here where it actually is a Bubble side issue or if it was something specific about your code that didn’t allow the updated token parameter to work.
Nope, must have been a coincidence. My apps started working again after several hours with the updated token format with no changes on my end. No clue.
