We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Description When a newly created Partner Admin tries to log in the first time it fails, as user.lastActiveAt is null:
user.lastActiveAt
null
Logging in the second time succeeds, as user.lastActiveAt is not null anymore.
To Reproduce Steps to reproduce the behavior:
Expected behavior: User should be logged in
On the backend side there is an exception thrown: TypeError: Cannot read properties of null (reading 'getDate')
/app/src/user/user.service.ts:250 updateUserDto.lastActiveAt.getDate() === user.lastActiveAt.getDate() ^ TypeError: Cannot read properties of null (reading 'getDate') at UserService.updateUser (/app/src/user/user.service.ts:250:66) at processTicksAndRejections (node:internal/process/task_queues:95:5)
Desktop
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Description
When a newly created Partner Admin tries to log in the first time it fails, as
user.lastActiveAt
isnull
:Logging in the second time succeeds, as
user.lastActiveAt
is notnull
anymore.To Reproduce
Steps to reproduce the behavior:
Expected behavior: User should be logged in
On the backend side there is an exception thrown: TypeError: Cannot read properties of null (reading 'getDate')
Desktop
The text was updated successfully, but these errors were encountered: