You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've encountered an issue where dataMessage.message is always null. Initially, after connecting, the data was received, but over time, only "empty" messages were sent.
Interestingly, there are other containers with identical settings but different numbers, and everything works fine there.
I would appreciate any help in resolving the issue or at least in identifying the cause.
That information comes directly from signal-cli, so I am afraid there is not much that I can do here. What you could try is a complete re-registration - i.e remove the signal-cli-config folder from the filesystem and register the number again.
The problem
Hello.
I've encountered an issue where dataMessage.message is always null. Initially, after connecting, the data was received, but over time, only "empty" messages were sent.
Interestingly, there are other containers with identical settings but different numbers, and everything works fine there.
I would appreciate any help in resolving the issue or at least in identifying the cause.
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?
JSON-RPC Mode
What's the architecture of your host system?
x86-64
Additional information
No response
The text was updated successfully, but these errors were encountered: