search

bbernhard / signal-cli-rest-api

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

some initial messages not sent #589

Open MilamberValheru opened 2 days ago

MilamberValheru commented 2 days ago

Today I wanted to start a little application using sign-cli-api. I added about 25 new numbers and my app should initiate communication with any of this numbers. It works for some, but unfortunatly 12 of them don't get any message. The numbers are correct and visible, I can contact them per hand from another account. I don't get any error from the v2/send - but the messages are not delivered.

API version is 0.88 using xmlrpc mode.

Looks like a bug, but maybe there is a log I can check somewhere?

bbernhard commented 2 days ago

Do you send a message to all of those recipients at once? Does it work if you send them a message exclusively? Could you please try to switch to the normal mode. Does it work then?

MilamberValheru commented 2 days ago

No, I send them one by one. I also repeated for a single number - no success. Normal mode will be tested (need my admin :) )

MilamberValheru commented 2 days ago

native mode has the same problem...

MilamberValheru commented 1 day ago

After one night and one day of work, we have most of the people online but not all:

Some didn't understand security settings about unhiding the phonenumber

For most the following workaround works:

So I assume:

What about new conversions to the signal-cli-api initiated by the other side? Can the api accept these chats automatically? This was not possible some time ago.

bbernhard commented 1 day ago

I haven't experienced any of the issues you've mentioned. It also depends which mode you are actually using. e.g the normal and native modes require you to call the receive mode regularily. If you are using the json-rpc mode, you don't have to deal with that.

The normal and native modes are easier to debug though, that's why I am often suggesting people to try these modes in case they experience issues. In order to debug the issues, please have a look here: https://github.com/bbernhard/signal-cli-rest-api/blob/master/doc/DEBUG.md

What about new conversions to the signal-cli-api initiated by the other side? Can the api accept these chats automatically?

What do you mean by that? If someone sends a message to the number that is registered with the API, you should receive that message via the receive endpoint. In normal/native mode this is done by polling the Signal Server. In json-rpc mode the messages are pushed from the Signal Server to the REST API service. That means you need to constantly have a Websocket connection established to the receive endpoint. If there's no Websocket listener, the message is lost.