Updated to version 1.20 and I get Uncaught (in promise) TypeError: can't convert null to object
Hi,
I update Twenty to the newest version and I get now this error:
Uncaught (in promise) TypeError: can't convert null to object
b9e https://crm.xxxx.xx/assets/index-a_yf5mtK.js:3510
EAt https://crm.xxxx.xx/assets/index-a_yf5mtK.js:3510
EAt https://crm.xxxx.xx/assets/index-a_yf5mtK.js:3510
r https://crm.xxxx.xx/assets/index-a_yf5mtK.js:3514
QIe https://crm.xxxx.xx/assets/index-a_yf5mtK.js:135
iit https://crm.xxxx.xx/assets/index-a_yf5mtK.js:135
N$ https://crm.xxxx.xx/assets/index-a_yf5mtK.js:48
iit https://crm.xxxx.xx/assets/index-a_yf5mtK.js:135
QIe https://crm.xxxx.xx/assets/index-a_yf5mtK.js:135
sat https://crm.xxxx.xx/assets/index-a_yf5mtK.js:135
n https://crm.xxxx.xx/assets/index-a_yf5mtK.js:3514
.....
17 Replies
I meant from 1.2 to 1.3
I installed temporarily a new instance with a fresh installation and got after reload the same
Hello @fendle
From what version were upgrading from ?
Also where do this log comes from ? I assume your browser console ?
Have you tried refreshing your server cache using:
- npx nx command:prod cache:flush
Hi @prastoin , I updated from 1.2.1 to 1.3 with docker compose
The logs are coming from the frontend
It looks like that a field has no value which is expected, but unfortunately it’s not telling which one
the first time when I login I see this:
companies as entry is shown but that's it as its running to the issue
on reload it's this:
I assume its this metadata call. That after the update there is a field expected which is not available or null. I assume there is a migration script missing?
Same (or very similar) issue here, also upgraded after Docker container to 1.2
Mhm I'm not aware of any data becoming not null here, could you guys share the failing request response error from the server ?
Same issue, also from the upgrade guide from v0.53 we are not suppoed to do any manual migrations?
Could you please share twenty server logs on error occurrence + browser failing request response body ? In order to determine what data is involved?
A new not null constraint might have been added without retro compatibility upgrade command
Can I message details in private?
Yes ofc, sent your a friend request
Can you confirm you received my messages?
Hey @Rorschach, will give this thread a look by the end of the day
Did receive your messages well
@Joaquim Ley @swin could you please share your workspace version in database located in
core.workspace.version
You might have not successfully upgraded to 1.3
Yes but it doesn't mean it would be sucessfullFair, I had to do a bunch of rollback and upgrades but it eventually worked, somehow the migrations corrected themselves, unfortunately I dont know the order I did
For followup @Rorschach workspace was blocked in 0.55