Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[bug] - User last active does not automatically update
See original GitHub issueDescribe the bug I think we created the field with the intention of updating it on login, but guessing forgot.
To Reproduce Logout Go to own map pin and see last active Login View map pin again (last active will not have changed)
Expected behavior
Likely will want a server-side or user store trigger that populates lastActive and modified on successful login. Server-side likely more reliable, but client side easier (could just add to existing userSignedIn field.
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Reassigned. Thanks @danitrod!
This should hopefully be fairly straight-forward, the userstore has a
userSignedInmethod which can be used to also update the last active once the user profile has been successfully loaded.The only complication would be with the
functions/src/userUpdates/backupUser.tsfunction, which by default creates a backup of the user whenever the profile is updated - which we probably don’t want to do if the only thing that is changing is the last active time. But it seems that function is not currently active (not sure why, but it would otherwise be called in thehandleUserUpdates), so probably would be good enough to just add a note to update it in the future if it becomes enabled again.Hi @nahos, are you working on this? Looks like it’s been a while, I’d like to work on it if you’re not.