Gmail Calendar error - Cannot read properties of undefined
Self hosting v0.52
After recently syncing my email/calendar, When I try to go to the calendar tab an error pops up: Cannot read properties of undefined (reading 'firstName') (screenshot attached)
I dont know if i missed something in the installation or there is something else wrong.
Error logs here:
Any help would be great. you guys have the start of a great project im excited to see how this develops

23 Replies
Can you have a look at your "workspaceMember" table and tell me if eveyone in you table has a firstname ?
You can use DBeaver of PgAdmin to do so
heya im going to play the noob card: i only see postgres, deafult, template0 and template1 databases in the twenty-db-1 container
which database should it live in?
or am i in the complete wrong area
if i look in the postgres database, i cannot find a workspaceMember table
Hey @WaveByteIT no worries
I think that Guillaume wanted you to look at your
core.user
table null firstname rowsI actually meant the workspaceMember table 🙂
it’s probably in the Postgres database @WaveByteIT
No worries there are no stupid questions. And if there are, I already asked them when starting on this project so no shame 🙂
Ah yeah sorry my bad ! Indeed located at
workspace_uuid.workspaceMember
might still be usefull to double check the core.user
valuecore user:
I see I am the core user on the database @Prastoin
@Guillaume
This is my only workspace member (me)
-[ RECORD 1 ]----+--------------------------------------
position | 0
nameFirstName | Steve
nameLastName | the Wiseman
colorScheme | System
locale | en
avatarUrl | profile-picture/original/...
userEmail | wavebyteit@gmail.com
userId | 382d69b7-c972-4c24-a977-50ff53f354b4
timeZone | system
dateFormat | SYSTEM
timeFormat | SYSTEM
searchVector | 'steve':1 'the':2 ...
id | 4139a153-2e5d-4c86-b42f-d802c71332a3
createdAt | 2025-03-17 21:33:59.810942+00
updatedAt | 2025-04-27 14:28:28.138098+00
deletedAt |

if i have missed anything, let me know i can fumble around the database
Sorry hard to go through your logs does workspace member has a value in its firstname column ?
yeah let me get the pgadmin so i can make it look better
i think i see my core.user has no first name
first/last name is null
@Prastoin for now ill format it this way
SELECT * FROM core.user;
Email: wavebyteit@gmail.com
First Name: NULL
Last Name: NULL
Email Verified: false
Account Disabled: false
Locale: en
Can Access Full Admin Panel: true
i see that the first name is empty for the core.user
Im happy to add this record in, but did i do something wrong when signing up/deploying the server?
as i added in first/last name to the core.user, docker compose down / up / migrate database i still get the same error.
Here are the logs in the email


To be honest this is the first time I hear of such an issue. You did nothing wrong, we may have missed a use case.
Let’s try first to make your app work. Can you manually add the first name manually in your database ? Restart docker and see if it works ?
Also, how did you signup : Email+password ? SignIn with Google ?
Good catch @prastoin for the core.users (however I don't think it's the table related from what i see in the
timeline-calendar-event.service
. Looks more coming from calendarEventParticipant
... if there are no person
, we fetch the workspaceMember
name.firstanme )i have added the first name / last name into the database and restarted docker > logs are above. computer still says no
i signed up with email+password
ok...
let me think
I need to spend a bit of time to try reproduce your error.
When you landed on this page, did you fill something ?

im pretty sure i did, it was a while ago.
We found a bug introduced recently. We are on it. Thanks for noticing
the man myth legend.
thanks
can you have a look at the table
featureFlag
in the core
schema and tell me if you see a row mentionning IS_NEW_RELATION_ENABLED
?
i dont see IS_NEW_RELATION_ENABLED record
thanks for taking the time to look at this, to be clear this is not urgent so if you have other priorities dont let this be taking up too much of your time
We found a fix. Will be released soon. You can watch the repository to find out more
@Guillaume @Prastoin thanks for your quick response. Thanks for your help!
team latest update fixed this issue
thanks!
thanks!
Great ! Enjoy coding !