[GH-ISSUE #32] Issue with sending follow up text #33

New issue

Open

opened 2026-03-02 23:33:08 +03:00 by kerem · 3 comments

kerem commented

2026-03-02 23:33:08 +03:00

Owner

Originally created by @AlenBeygelman on GitHub (Sep 7, 2022).
Original GitHub issue: https://github.com/airmessage/airmessage-server/issues/32

For specific numbers, after sending the first text, a follow up text will not work. Only solution is to clear the chat and start over.

Originally created by @AlenBeygelman on GitHub (Sep 7, 2022). Original GitHub issue: https://github.com/airmessage/airmessage-server/issues/32 For specific numbers, after sending the first text, a follow up text will not work. Only solution is to clear the chat and start over. ![WhatsApp Image 2022-09-07 at 9 46 33 AM (1)](https://user-images.githubusercontent.com/45246233/188990013-7fd510d2-3379-4d26-ad92-c089fd1ef373.jpeg) ![WhatsApp Image 2022-09-07 at 9 46 33 AM](https://user-images.githubusercontent.com/45246233/188990019-88ac28a6-82b7-483c-b49f-d4f251a1427d.jpeg)

kerem commented

2026-03-02 23:33:09 +03:00

Author

Owner

@tagavari commented on GitHub (Sep 7, 2022):

Thanks for reporting this!

When creating a chat with a server on macOS 11+, the app will do a little dance where it creates the conversation on the fly as soon as the first message is sent. It's possible that it's failing to associate this new conversation properly with the original one you created.

Do you notice a pattern that causes conversations with certain addresses to fail?

@tagavari commented on GitHub (Sep 7, 2022): Thanks for reporting this! When creating a chat with a server on macOS 11+, the app will do a little dance where it creates the conversation on the fly as soon as the first message is sent. It's possible that it's failing to associate this new conversation properly with the original one you created. Do you notice a pattern that causes conversations with certain addresses to fail?

kerem commented

2026-03-02 23:33:09 +03:00

Author

Owner

@AlenBeygelman commented on GitHub (Sep 8, 2022):

I updated my account to a new apple id which created a new thread with this address. I do not know what I should do now to fix this disassociation that you are describing.

@AlenBeygelman commented on GitHub (Sep 8, 2022): I updated my account to a new apple id which created a new thread with this address. I do not know what I should do now to fix this disassociation that you are describing.

kerem commented

2026-03-02 23:33:09 +03:00

Author

Owner

@working-name commented on GitHub (Sep 11, 2022):

For me this happens when the machine running airmessage server does not have a particular email or phone number checked as "I can be reached at". The conversation was somehow started from another email or phone number so you basically have to get back to the server machine and start a new conversation from the desired phone number (essentially a new thread for the same person but with your current/desired phone number or email)

@working-name commented on GitHub (Sep 11, 2022): For me this happens when the machine running airmessage server does not have a particular email or phone number checked as "I can be reached at". The conversation was somehow started from another email or phone number so you basically have to get back to the server machine and start a new conversation from the desired phone number (essentially a new thread for the same person but with your current/desired phone number or email)