Upgrade from 1.0 > 1.3 broke twenty
After a recent upgrade i v1.3 I get "an error occured" when logging in. And container logs for twenty-server says this:
I upgraded from 1.0 to 1.1 to 1.2 to 1.3.
I made a db backup in between all upgrades.
Not sure if these translation errors have anything to do with the actual problem preventing me from logging in.
Are there other logs I should check?
Is this a known issue?
Did I miss some post-upgrade steps?
27 Replies
seams to be the same issue thats discussed here:
https://discord.com/channels/1130383047699738754/1406698879575130254
I just upgraded to 1.4.0 now.
After the upgrade, I still get the blank screen....
If I change to a new browser which has not logged into twenty, I can log in and then I get this briefly:

@EbenezerIbiza let's work from there
could you share your network tab and specifically the faily requests errors?
Btw. this error disappears WAAAY too fast. Please consider having errors stay around.
Yeah, no failed requests. All 200 OK

I hope this was what you meant?
I have this also. Not sure if relevant

filter on XHR requests
I think the metadata queries are actually returning errors, could you check their response
it's 200 but that's because graphql standard requires it to always be 200 and errors are embed in the response
I have tried filtering on XHR. Not sure what I am looking for though

Click on the
file
column it will expand the view then look for Response
tab
this one seems fine, could you repeat it for the 3 other above it?



Is this what you're looking for?
I dont see any errors in this
Yes, but your backend seems fine
Thats good, I guess 🙂
Could you DM me this full console log
Sure
From firefox or from containers?
Firefox

Tried to DM you
Sent you a friend request
seems to be throwing the error here
So is this unrelated to the stuff that was fixed in 1.4?