Simple-SMS-Messenger icon indicating copy to clipboard operation
Simple-SMS-Messenger copied to clipboard

Sends SMS to wrong contact

Open dmillman opened this issue 1 year ago • 18 comments

Simple SMS Messenger 5.18.1 Simple Contacts Pro 6.22.3 Google SMS and contacts apps disabled

  1. Open Simple SMS Messenger
  2. Select an existing conversation
  3. Type a message
  4. Click send

Observed: The message appears to send normally and can be seen at the bottom in the conversation, but was sent to the wong person If you leave the conversation and return to it, the message no longer appears If you open the conversation with the person who it was actualy sent to, it does appear Confirmed with the (wrong) recipient that it was received. Every message to this number is sent to the same wrong number.

Expected: Messages should be sent to the correct people.

Background: This happened several times with an older ver, but with different users Upgraded to 5.18.1 to see if it was fixed, but can still reproduce

dmillman avatar Apr 23 '23 19:04 dmillman

can you reproduce it reliably? Doesnt the given contact have multiple phone numbers?

tibbi avatar Apr 23 '23 20:04 tibbi

I reproduced it 4 times today. It happened every time. The contact that was getting the messages is not someone I want to annoy any more than I have.

Each of the two contacts has only one single "Mobile" number.

dmillman avatar Apr 24 '23 01:04 dmillman

I dont see how would that be possible, hasnt happened to others either.. Do they at least have a similar number, name or something?

tibbi avatar Apr 24 '23 07:04 tibbi

No, the numbers are not similar. I was thinking that the I might have contacts corruption. The last time this happened, it was the same contact receiving messages, but the contact I was sending to was different.

dmillman avatar Apr 24 '23 10:04 dmillman

it will be some system issue, it never happened in other apps?

tibbi avatar Apr 24 '23 10:04 tibbi

no

dmillman avatar Apr 24 '23 23:04 dmillman

Came here for looking an answer to the same issue that occurred to me as well.

  • LineageOS 19.1 with Microg
  • Simple SMS Messenger 5.18.1 from github Contact with a single mobile number like (732) 555-1234 No prior messages or threads with contact Sent message, from character count, the message should have been sent as MMS. Got text from number (908) 555-1234 that i sent sms to wrong number, The original sent message and the reply received showed in separate threads. I cannot troubleshoot this further as I immediatly switched apps, I do not afford to think that a message was sent and in fact it wasn't never mind that content went to wrong destination The area codes that were involved are for real, my phone number starts with 908, provider Verizon

lleo19 avatar May 01 '23 18:05 lleo19

Same thing happened to me. I'm on android 11. The app version was 5.18.1.

Kitayoki avatar May 10 '23 22:05 Kitayoki

I have the same issue with the latest version on a Google Pixel 7a with Android 13

bartlibert avatar May 21 '23 09:05 bartlibert

Hi, same here. Seems to happen especially with new contacts - ones that are new or non existent to the address book; and/or are new to the SMS app.

I'm trying to send an SMS to a $newcontact telephone number; now a $randomprevious number from my previous SMS's shows up.

For some reason, this $randomprevious number keeps popping up in place where I expect $newcontact. Even if I type the $newcontact number manually (i.e. I enter +316NNNNNN for SMS number). I find it utterly weird that the messed up number keeps popping up - even if I copy the new contact to a new name in the address book. up the number seems to be repeatable, i.e. once a number has been messed up, it is not possible to use their "real" number - the messed up number comes in its place.

I have seen this behaviour twice now, with different telephone numbers.

vsessink avatar Jun 05 '23 13:06 vsessink

I've stopped using Simple-SMS-Messenger because of this. Sending messages to the wrong recipient is too harsh a bug.

When this is fixed, I will go back to using Simple-SMS-Messenger.

dmillman avatar Jun 05 '23 14:06 dmillman

so is the issue always caused by the country number at the front? Or sometimes the message is sent to a seemingly random contact that has a whole different number?

tibbi avatar Jun 25 '23 21:06 tibbi

In my case:

  • both the contact I tried to send to and the contact to whom it was actually sent were in the same country
  • the contact I sent to did not have a country code in its number
  • the contact to whom it was actually sent did have a country code in its number (1)

dmillman avatar Jun 25 '23 21:06 dmillman

well, I thought I described it quite clearly: I tried to send an MMS (due to text size, no attachment) to a contact, and message was sent to same number but different area code, both in the same country +1

tried to send it to +1 732 555-1234 and got it sent to +1 908 555-1234  The number +1 908 555-1234 was not in my contacts, it is a stranger.

so only the area code was substituted.

My own phone number area code is 908. The contact in my contacts has the right area code showing. I do not think it has country code, i.e. +1

hope this helps.

-----Original message----- From: @.> Sent: Sunday June 25th, 2023 21:29 To: SimpleMobileTools/Simple-SMS-Messenger @.> Cc: Lorant Leopold @.>; Comment @.> Subject: Re: [SimpleMobileTools/Simple-SMS-Messenger] Sends SMS to wrong contact (Issue #640)

In my case:

  • both the contact I tried to send to and the contact to whom it was actually sent were in the same country
  • the contact I sent to did not have a country code in its number
  • the contact to whom it was actually sent did have a country code in its number (1)

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>

lleo19 avatar Jun 25 '23 23:06 lleo19

I am also experiencing this issue - I send a message to a desired recipient, then back out and see the wrong recipient in the message list has received it. They respond to verify that I did indeed message the wrong person. Has happened 4-5 times today. Google Pixel Fold Android 13 (default AOSP) SMS version 5.18.2 (from F-Droid)

themichaelolson avatar Jul 01 '23 22:07 themichaelolson

Hit me today. Responded to an SMS from a contact, it was sent to another number. Couldn't believe what I saw and sent another message, it went to the same wrong number. That number is not in my contacts; I cannot rule out that it belongs to a contact that I have deleted at some point. Both numbers have the same country code. Fairphone 4 Android 12 Carddav address book via davx5 SMS 5.18.2 via F-Droid

kiber42 avatar Aug 23 '23 18:08 kiber42

DAVx5 here, too, synchronizing with an owncloud cardav service. Both SMS and address book are Simplemobiletools'.

vsessink avatar Aug 23 '23 19:08 vsessink

I have super frequently the same issue. I just disabled the app and switched back to Google app :'( To me, the easy way to reproduce it is to try to send a message to a number only (no corresponding contact). The app says "no contact" (OK normal) but when I start the conversation it uses a contact. Then, later, my contact reply saying "hey dude, wrong number". So I try to reply to him "shit, I don't like you, it was not for you then" but this reply is actually sent to again another contact of mine... hence, I removed the app. I tried to select the right contact to reply to but never succeeded.

samlemarnais avatar Sep 20 '23 15:09 samlemarnais