Details
Pressing "Secondary device logout" dev button makes primary device print a log:
LOG Decrypted message from device mJc0HgRtPM1WTp+SWy/VE4C+243IznJPf2TGvriZ4A4: {"type":"LOG_OUT_SECONDARY_DEVICE"}
Diff Detail
- Repository
- rCOMM Comm
- Lint
No Lint Coverage - Unit
No Test Coverage
Event Timeline
lib/actions/user-actions.js | ||
---|---|---|
64–65 | can be merged | |
246 | debug leftover? | |
263–273 |
makes sense However, in that case, you should first attempt to encrypt, and only if the session does not exist call createOlmSessionWithPeer - if there is a session this code will overwrite the existing one and use the new session to encrypt which could cause some issues, and is not what we want. | |
279–282 | what if the user e.g. has no internet connection but logs out anyway and his device cannot send messages through TB? |
lib/actions/user-actions.js | ||
---|---|---|
263–273 | Good to know, I'll add a try-catch | |
279–282 | Created a task to discuss it: https://linear.app/comm/issue/ENG-8380/log-out-with-no-internet-connection |