-
Notifications
You must be signed in to change notification settings - Fork 26
Unable to send messages using latest build #31
Comments
that's because signal is starting to disable sending message by phone number and also you can't get the public key anymore: Therefore i am writing the support for the contact discovery service. |
To fetch the uuid and then send the message to the uuid. With that latest version, try to reset the conversation, then textsecure gets the uuid |
try this branch: https://github.com/signal-golang/textsecure/tree/new_contacts |
Ah, okay. Just had a quick look into the branch already. Will try and let you know. As always, thanks for the work!! |
One, question though. I use the CLI for 2FA with Nextcloud. Do you have an ETA, when the sending by number wont work anymore without your #27? |
compiled w/
|
Do you have added the user you are sending to the contacts? |
Via id or via tel ? |
I have added a WriteContactsToPath() call in the GetRegisteredContacts() so it should update the contacts.yml with the uuid and can you try if it works when you change in cmd/textsecure/main.go line 580 to |
The |
Hint: It works for devices already present (sent messages in the past). It just fails for any new device. |
I missed the correct byte to string mapping for uuids, see if 16b9c60 works |
Ahhh....yes, it works! |
Update: works for single contact, not for groups (might be missing code in cli ... something related to the |
054ae62 maybe this? |
Hehe... works with group, but doesn't work with single contacts anymore ;) Sending to group does segfault also. Group:
Sending to single contact works for one device (desktop client) but my mobile just shows the same error as above (
|
i found a check for invalid pointer, the problem is, we don't save uuid's for group members that aren't in our contact list, yet |
I had to merge it, will work further on the groups uuid, the merge request already improves the situation |
For me with the latest build |
I'm encountering this behaviour with the latest build in a different way: Although, I am getting the messages on the textsecure client, when sending it from the Desktop App. The debug log:
Resetting the Session on the Desktop App doesn't make it work. Interestingly, when resetting the session on the Desktop Client, I am not able to send a message to the textsecure client with the Desktop Client (Mobile works fine) Any Ideas? :-) |
Actually what's wrong here is, that |
NUMBER was in this Case the Phone Number and Not the UUID. |
I've just rebuild the signal commandline binary using the latest build and can't send messages.
The log says:
The mobile phone only says "Unterhaltungssitzung aktualisert"
The text was updated successfully, but these errors were encountered: