Upon creating a new conversation (+ > New Message), entering an ID with leading whitespace, and sending a message, the Session application will cease to function. If closed, it will not be able to reopen for the current user.
This is caused by the whitespace being saved in the id column of the conversations table, resulting in check_session_id failing with the message Invalid session ID: expected 66 hex digits starting with 05, and the application not proceeding beyond the splash screen.
Once this has happened, the only way to fix it is to manually edit db.sqlite and remove the offending row.
Expected Behavior
Either:
An error indicating the format of the ID is incorrect
The whitespace is stripped, and the conversation is created successfully
Steps To Reproduce
Create a new conversation ( + > New Message )
In "Enter Session ID or ONS Name", enter a space followed by a valid Session ID
Click Next
Send a message
Desktop Version
v1.11.0
Anything else?
Platform: Debian Linux 6.1.27-1 x86_64
Commit: 448c9dc14bd64eebae03676e360bf78ae2a54920
Code of conduct
Self-training on how to write a bug report
Is there an existing issue for this?
Current Behavior
Upon creating a new conversation (+ > New Message), entering an ID with leading whitespace, and sending a message, the Session application will cease to function. If closed, it will not be able to reopen for the current user.
This is caused by the whitespace being saved in the id column of the conversations table, resulting in
check_session_idfailing with the messageInvalid session ID: expected 66 hex digits starting with 05, and the application not proceeding beyond the splash screen.Once this has happened, the only way to fix it is to manually edit db.sqlite and remove the offending row.
Expected Behavior
Either:
Steps To Reproduce
Desktop Version
v1.11.0
Anything else?
Platform: Debian Linux 6.1.27-1 x86_64 Commit: 448c9dc14bd64eebae03676e360bf78ae2a54920