search

bbernhard / signal-cli-rest-api

Dockerized Signal Messenger REST API
https://bbernhard.github.io/signal-cli-rest-api/
MIT License
1.37k stars 160 forks source link

dataMessage.message is always null #581

Open wking0702 opened 2 months ago

wking0702 commented 2 months ago

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.

{
   "envelope":{
      "source":"+38096ХХХХХХ",
      "sourceNumber":"+38096ХХХХХХХ",
      "sourceUuid":"0ХХХХ",
      "sourceName":"Username ",
      "sourceDevice":1,
      "timestamp":1722238386596,
      "dataMessage":{
         "timestamp":"7XXXXXX",
         "message":null,
         "expiresInSeconds":0,
         "viewOnce":false
      }
   },
   "account":"+3809ХХХХХХХХХХХ"
}

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

bbernhard commented 2 months ago

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.