You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've used vuex-oidc for quite some time in our application and it's a really nice library. Thanks a lot for your work!
If a user comes to our application we use getOidcUser to check if the user has an "old" login. However, after the last update the application always throws an error when calling getOidcUser while not logged in:
Uncaught (in promise) TypeError: Cannot read properties of null (reading 'expires_at')
at Store.setOidcUser (vuex-oidc.esm.js:626:31)
at wrappedMutationHandler (vuex.esm.js:853:13)
Because even if the user is null, it still tries to access user.expires_at which then fails with an error.
Is this on purpose or is there simply a check missing? If so, I suggest adding a check or something similar to prevent the library from throwing this error when trying to get the user while not logged in.
Thank you!
The text was updated successfully, but these errors were encountered:
Sorry about this, it looks like a mistake. I’m on the road right now, but will fix this by the end of the month. Meanwhile you will have to roll back to v3.10.3 to get rid of this errror.
We've used vuex-oidc for quite some time in our application and it's a really nice library. Thanks a lot for your work!
If a user comes to our application we use
getOidcUser
to check if the user has an "old" login. However, after the last update the application always throws an error when callinggetOidcUser
while not logged in:This is cause by:
vuex-oidc/src/store/create-store-module.js
Line 423 in d6c667f
Because even if the user is null, it still tries to access
user.expires_at
which then fails with an error.Is this on purpose or is there simply a check missing? If so, I suggest adding a check or something similar to prevent the library from throwing this error when trying to get the user while not logged in.
Thank you!
The text was updated successfully, but these errors were encountered: