search

michaelkourlas / voipms-sms-client

Popular Android messaging app for VoIP.ms, a Canadian VoIP provider
https://play.google.com/store/apps/details?id=net.kourlas.voipms_sms
Apache License 2.0
216 stars 51 forks source link

0.6.26-fdroid - getting lots of "not sent, touch to try again" errors. -- in all (known) cases SMS is actually being sent #267

Closed UPBT closed 5 months ago

UPBT commented 5 months ago

I got these occasionally on 0.6.25-fdroid too over the last several months, but I seem to recall that it was almost always a connectivity issue on my end, and the messages were not actually sent.

Because "butt-dial" and because the "unsent" message remains "touch sensitive" I've managed to send one text multiple times as the phone rattled around in my pocket. (Edit to add: 98% sure it does it while sitting untouched on my desk, see follow up message.)

The first time this error happened, I sent the message multiple times, merely because I believed the error message was accurate. As stated already, the message was successfully sent but I still got the error message in the app.

I'm not sure if each SMS is sent with a unique message ID in the "overhead" or not. In lieu of me setting up wireshark to find out before posting this report, here's a random person's blog post that may or may not be helpful.

https://www.telecomhall.net/t/how-much-overhead-is-used-to-send-the-message-k-back-to-an-sms/21239

If there is a "unique ID" for every try, I would expect voip.ms to pass on identical messages with different "unique IDs" -- I also don't know the process of showing the "not sent, touch to try again" error. Is it just shown after a too-long lack of response from voip.ms?

I'm also pretty sure I just saw the api error 'missing_method' flash on my screen, once.

I installed 0.6.26-fdroid just about as soon as it was available, and could imagine a possible DDoS of the servers for everyone syncing for the first time in over a week.

UPBT commented 5 months ago

For anyone getting the same odd error, to keep the app from sending or trying to resend multiple times (correction from above, it just happened again and I'm 98% I didn't "butt-dial" this time)

  1. toggle off internet (probably excessive, a "belt and suspenders" step), and
  2. long-press on unsent text message
  3. At the top of the screen some icons will appear, press on the "trash can"
UPBT commented 5 months ago

I'm not sure if each SMS is sent with a unique message ID in the "overhead" or not.

OK, a "long press" :: "info" clearly shows that each of the text message re-sends has a different ID.

The issue might be a slow response, or a no-response from voip.ms for the specific text message. Secret Cloudflare API changes might be slowing down the "message -- response" time. (I've logged in multiple times over the last week to send messages from their beta SMS/MMS portal and the logging in has been annoyingly slow)

I should also mention that all occurrences happens while I was on WiFi

UPBT commented 5 months ago

Whelp, apparently no one else has had this issue, and the issue seems to have resolved itself -- zero problems in the last 5 days for me.

If voip.ms fixed something on their end, they of course should have *cough* *cough* fully documented the change somewhere on their website; which is where I'll look next, (after I figure out if I can close my own ticket.)

Awfully mysterious how this fixed itself...