The problem
Is it possible for signal-cli(-rest-api) to notify the Signal service that it has "read" a message with receipts disabled at the account level? This action works when using Signal's desktop & iOS clients, but so far I've been unable to get it to work with signal-cli-rest-api. Attempts to send "read" or "viewed" receipts return a "204 No Content" with no string. The behavior is unchanged even when testing after enabling read receipts on the accounts of both the sender & receiver.
The way it works for me between Signal's desktop & iOS clients is:
- Send a message to a recipient contact
- Observe notification of new message on both clients of the recipient
- Open chat to view new message on one of the recipient’s clients
- Observe notification removed from the other recipient client
Are you using the latest released version?
Have you read the troubleshooting page?
What type of installation are you running?
signal-cli-rest-api Docker Container
In which mode are you using the docker container?
Native Mode
What's the architecture of your host system?
x86-64
Additional information
No response
The problem
Is it possible for signal-cli(-rest-api) to notify the Signal service that it has "read" a message with receipts disabled at the account level? This action works when using Signal's desktop & iOS clients, but so far I've been unable to get it to work with signal-cli-rest-api. Attempts to send "read" or "viewed" receipts return a "204 No Content" with no string. The behavior is unchanged even when testing after enabling read receipts on the accounts of both the sender & receiver.
The way it works for me between Signal's desktop & iOS clients is:
Are you using the latest released version?
Have you read the troubleshooting page?
What type of installation are you running?
signal-cli-rest-api Docker Container
In which mode are you using the docker container?
Native Mode
What's the architecture of your host system?
x86-64
Additional information
No response