issue: https://linear.app/comm/issue/ENG-5281/refactor-logout-and-deleteaccount-actions
We need to remove the id field from LoggedOutUserInfo, because it doesn't make sense in multikeyserver world for the keyserver to set some user id for the logged out user. It wasn't really being used anyway - right after the app is freshly built, the whole currentUserInfo is null. I couldn't just make it null though, because the app was behaving incorrectly then (see the linear issue's comments)
Details
Details
Tested that it is possible to log out and back in. No errors show up.
Ran yarn flow-all.
TESTED OLD CLIENTS:
- Built the client on master, without this diff applied
- Ran metro, opened the app
- Killed metro
- Ran the keyserver on this branch, with this diff applied
- Logged out
- Logged in
No errors appeared on keyserver console, checked in redux devtools that logout and login actions were successful. The client didn't show any errors.
The currentUserInfo after logout was {anonymous: true}, but this didn't cause any problems - I clicked around on the login/register screens and no errors showed up. I was able to register a new user (I used the new registration flow). This is consistent with the theory this diff is based on - that the id wasn't begin used when not logged in
Diff Detail
Diff Detail
- Repository
- rCOMM Comm
- Branch
- inka/actions_new_branch
- Lint
No Lint Coverage - Unit
No Test Coverage
Event Timeline
Comment Actions
Will this break logging out on older clients?
Testing this should be added to this diff's test plan. I think it should be okay, since clients typically log out immediately rather than waiting for the server's response, but I'm not sure if there will be some weird side effects that cause the app to crash if the id is expected but missing.