Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't contact Ex-TextSecure users #1253

Closed
graingert opened this issue Mar 27, 2014 · 24 comments
Closed

Can't contact Ex-TextSecure users #1253

graingert opened this issue Mar 27, 2014 · 24 comments

Comments

@graingert
Copy link

I can't contact an Ex-TextSecure user, who's android phone broke and who has now moved his sim to another phone.

All sent messages to this contact are sent as "blue" WhatsApp mode messages, and are stuck in pending forever.

@mcginty
Copy link
Contributor

mcginty commented Mar 27, 2014

How long has it been since this happened? After some amount of time with no connection, GCM should eventually notify the TextSecure server that their client is no longer reachable, and they will be automatically deregistered.

@graingert
Copy link
Author

It's been several days
On 27 Mar 2014 22:51, "Jake McGinty" notifications@github.com wrote:

How long has it been since this happened? After some amount of time with
no connection, GCM should eventually notify the TextSecure server that
their client is no longer reachable, and they will be automatically
unsubscribed.

Reply to this email directly or view it on GitHubhttps://github.com//issues/1253#issuecomment-38870931
.

@generalmanager
Copy link

@graingert You probably already know this, but you can force sending an SMS in the current version 2.0.5 by disabling wifi and mobile data for the time you are sending the message.

In the next version you should be able to long-click the send button to force sending an SMS.
It's not a real solution, but could help until he gets deregistered automatically.

@graingert
Copy link
Author

I need to be able to force sending a plaintext SMS

@generalmanager
Copy link

@graingert you can do so by ending the encrypted session. Just click on the lock icon on the top before doing what I described before.

@graingert
Copy link
Author

but there isn't a lock item at the top...

@generalmanager
Copy link

Then it will automatically be sent in plain text.
Just turn off your wifi and mobile internet for the few seconds while sending the message and it will be delivered via plaintext sms.
The next version of TextSecure will allow to do this with a long click on the send button.

@graingert
Copy link
Author

The message is now stuck in "transport: PENDING"

@graingert
Copy link
Author

@generalmanager thanks for your help, by the way

@graingert
Copy link
Author

I think this is failing for me because the SMS transport is broken by my
network provider
On 28 Mar 2014 10:02, "generalmanager" notifications@github.com wrote:

Then it will automatically be sent in plain text.
Just turn off your wifi and mobile internet for the few seconds while
sending the message and it will be delivered via plaintext sms.
The next version of TextSecure will allow to do this with a long click on
the send button.

Reply to this email directly or view it on GitHubhttps://github.com//issues/1253#issuecomment-38903461
.

@generalmanager
Copy link

If your main problem is solved (and your current one doesn't have anything to do with it), could you please close this ticket?
And if your buddy still isn't deregistered, somebody has built a ruby script to unregister from the whisperpush server: #622 (comment)

With a little effort this should probably work with the textsecure server as well.

@graingert
Copy link
Author

Regular SMS messages are working for everyone else. But I can't send any messages to this particular user, even with data/WiFi disabled or choosing to send unencrypted. Also the UI slows to a crawl in this mode.

@Wopfi
Copy link

Wopfi commented Sep 9, 2014

I got the same Issue here. One of my Contacts switched to an iPhone and forgot to unregister by disabling the Push Messages. Since then I am unable to send him Messages. It's been several weeks now but Textsecure still tries to send Push Messages. It doesnt even work if i push the "Send" Button long and choose SMS. Sending SMSes to other Contacts works normally.

@tinloaf
Copy link
Contributor

tinloaf commented Sep 9, 2014

Could you post a debug log (settings -> all the way down) immediately after trying to send an unencrypted SMS to this person?

@Wopfi
Copy link

Wopfi commented Sep 9, 2014

Here you are:
http://hastebin.com/noqaqezuti

@tinloaf
Copy link
Contributor

tinloaf commented Sep 9, 2014

Thanks. To me it looks like it's trying to send an actual SMS, not a TextSecure message, but @moxie0 is better at judging that than me. Saving the relevant parts here:

W/Session (10632): Checking session...
W/MmsSmsDatabase(10632): Executing query: SELECT _id, body, type, thread_id, address, address_device_id, subject, date_sent, date_received, m_type, msg_box, status, part_count, ct_l, tr_id, m_size, exp, st, transport_type FROM (SELECT DISTINCT date_sent * 1 AS date_sent, date * 1 AS date_received, _id, body, read, thread_id, type, address, address_device_id, subject, NULL AS m_type, NULL AS msg_box, status, NULL AS part_count, NULL AS ct_l, NULL AS tr_id, NULL AS m_size, NULL AS exp, NULL AS st, 'sms' AS transport_type FROM sms WHERE (thread_id = 9) UNION ALL SELECT DISTINCT date * 1000 AS date_sent, date_received * 1000 AS date_received, _id, body, read, thread_id, NULL AS type, address, address_device_id, NULL AS subject, m_type, msg_box, NULL AS status, part_count, ct_l, tr_id, m_size, exp, st, 'mms' AS transport_type FROM mms WHERE (thread_id = 9) ORDER BY date_received ASC)
W/KeyCachingService(10632): Incrementing activity count...
W/MmsCommunication(10632): Getting MMSC params for apn null
W/MmsCommunication(10632): Android won't let us query the APN database.
W/MmsSmsDatabase(10632): Executing query: SELECT _id, body, read, type, address, address_device_id, subject, thread_id, status, date_sent, date_received, m_type, msg_box, part_count, ct_l, tr_id, m_size, exp, st, transport_type FROM (SELECT DISTINCT date_sent * 1 AS date_sent, date * 1 AS date_received, _id, body, read, thread_id, type, address, address_device_id, subject, NULL AS m_type, NULL AS msg_box, status, NULL AS part_count, NULL AS ct_l, NULL AS tr_id, NULL AS m_size, NULL AS exp, NULL AS st, 'sms' AS transport_type FROM sms WHERE (read = 0) UNION ALL SELECT DISTINCT date * 1000 AS date_sent, date_received * 1000 AS date_received, _id, body, read, thread_id, NULL AS type, address, address_device_id, NULL AS subject, m_type, msg_box, NULL AS status, part_count, ct_l, tr_id, m_size, exp, st, 'mms' AS transport_type FROM mms WHERE (read = 0) ORDER BY date_received ASC)
I/Timeline(10632): Timeline: Activity_idle id: android.os.BinderProxy@428f6288 time:42916270
W/MediaPlayer-JNI(10632): MediaPlayer finalized without being released
W/Session (10632): Checking session...
W/ConversationActivity(10632): Sending message...
W/MmsSmsDatabase(10632): Executing query: SELECT _id, body, type, thread_id, address, address_device_id, subject, date_sent, date_received, m_type, msg_box, status, part_count, ct_l, tr_id, m_size, exp, st, transport_type FROM (SELECT DISTINCT date_sent * 1 AS date_sent, date * 1 AS date_received, _id, body, read, thread_id, type, address, address_device_id, subject, NULL AS m_type, NULL AS msg_box, status, NULL AS part_count, NULL AS ct_l, NULL AS tr_id, NULL AS m_size, NULL AS exp, NULL AS st, 'sms' AS transport_type FROM sms WHERE (thread_id = 9) UNION ALL SELECT DISTINCT date * 1000 AS date_sent, date_received * 1000 AS date_received, _id, body, read, thread_id, NULL AS type, address, address_device_id, NULL AS subject, m_type, msg_box, NULL AS status, part_count, ct_l, tr_id, m_size, exp, st, 'mms' AS transport_type FROM mms WHERE (thread_id = 9) ORDER BY date_received DESC) LIMIT 1
W/SMSSender(10632): Got message id for new message: 2942
W/Session (10632): Checking session...
W/SmsSender(10632): Sending message: 2942
W/MessageDatabase(10632): Updating ID: 2942 to base type: 22
W/MmsSmsDatabase(10632): Executing query: SELECT _id, body, type, thread_id, address, address_device_id, subject, date_sent, date_received, m_type, msg_box, status, part_count, ct_l, tr_id, m_size, exp, st, transport_type FROM (SELECT DISTINCT date_sent * 1 AS date_sent, date * 1 AS date_received, _id, body, read, thread_id, type, address, address_device_id, subject, NULL AS m_type, NULL AS msg_box, status, NULL AS part_count, NULL AS ct_l, NULL AS tr_id, NULL AS m_size, NULL AS exp, NULL AS st, 'sms' AS transport_type FROM sms WHERE (thread_id = 9) UNION ALL SELECT DISTINCT date * 1000 AS date_sent, date_received * 1000 AS date_received, _id, body, read, thread_id, NULL AS type, address, address_device_id, NULL AS subject, m_type, msg_box, NULL AS status, part_count, ct_l, tr_id, m_size, exp, st, 'mms' AS transport_type FROM mms WHERE (thread_id = 9) ORDER BY date_received DESC) LIMIT 1
W/SMSReceiverService(10632): Intent resultcode: -1
W/SMSReceiverService(10632): Running sent callback: 2942
W/MessageDatabase(10632): Updating ID: 2942 to base type: 23
W/MmsSmsDatabase(10632): Executing query: SELECT _id, body, type, thread_id, address, address_device_id, subject, date_sent, date_received, m_type, msg_box, status, part_count, ct_l, tr_id, m_size, exp, st, transport_type FROM (SELECT DISTINCT date_sent * 1 AS date_sent, date * 1 AS date_received, _id, body, read, thread_id, type, address, address_device_id, subject, NULL AS m_type, NULL AS msg_box, status, NULL AS part_count, NULL AS ct_l, NULL AS tr_id, NULL AS m_size, NULL AS exp, NULL AS st, 'sms' AS transport_type FROM sms WHERE (thread_id = 9) UNION ALL SELECT DISTINCT date * 1000 AS date_sent, date_received * 1000 AS date_received, _id, body, read, thread_id, NULL AS type, address, address_device_id, NULL AS subject, m_type, msg_box, NULL AS status, part_count, ct_l, tr_id, m_size, exp, st, 'mms' AS transport_type FROM mms WHERE (thread_id = 9) ORDER BY date_received DESC) LIMIT 1
W/SystemStateListener(10632): java.lang.IllegalArgumentException: Receiver not registered: org.thoughtcrime.securesms.service.SystemStateListener$ConnectivityListener@4198cc10
W/SystemStateListener(10632):   at android.app.LoadedApk.forgetReceiverDispatcher(LoadedApk.java:665)
W/SystemStateListener(10632):   at android.app.ContextImpl.unregisterReceiver(ContextImpl.java:1517)
W/SystemStateListener(10632):   at android.content.ContextWrapper.unregisterReceiver(ContextWrapper.java:489)
W/SystemStateListener(10632):   at org.thoughtcrime.securesms.service.SystemStateListener.unregisterForConnectivityChange(SystemStateListener.java:46)
W/SystemStateListener(10632):   at org.thoughtcrime.securesms.service.SmsSender.unregisterForRadioChanges(SmsSender.java:180)
W/SystemStateListener(10632):   at org.thoughtcrime.securesms.service.SmsSender.handleSentMessage(SmsSender.java:145)
W/SystemStateListener(10632):   at org.thoughtcrime.securesms.service.SmsSender.process(SmsSender.java:64)
W/SystemStateListener(10632):   at org.thoughtcrime.securesms.service.SendReceiveService$SendReceiveWorkItem.run(SendReceiveService.java:273)
W/SystemStateListener(10632):   at org.thoughtcrime.securesms.util.WorkerThread.run(WorkerThread.java:46)
W/KeyCachingService(10632): Decrementing activity count...
W/KeyCachingService(10632): Incrementing activity count...

@Wopfi
Copy link

Wopfi commented Sep 9, 2014

Oh, sorry, I thought you wanted me to send an actual SMS, which doesn't work either.
I also tried to send a Push Message before but i think the Log got reset just after that so it doesn't show.

@tinloaf
Copy link
Contributor

tinloaf commented Sep 9, 2014

No, that's exactly what I wanted. I was trying to say that it looks as if TextSecure behaves correctly (hand over an SMS message to Android), but it gets stuck somewhere. Looking at it again, the

W/SMSReceiverService(10632): Intent resultcode: -1

looks strange.

@moxie0
Copy link
Contributor

moxie0 commented Sep 9, 2014

That log is sending an SMS. If it's not reaching your friend, it's a problem with the network or the Android ROM.

@graingert
Copy link
Author

I had the same issue, I made my friend register and de-register on another phone and now everything works fine. Also fixing the battery life and data useage issue I was having with text secure.

I think it was probably retrying the "Blue" push messages while True

@Wopfi
Copy link

Wopfi commented Sep 13, 2014

The strange thing is, that I can reach all other non TextSecure Contacts via SMS without Problems.

@tinloaf
Copy link
Contributor

tinloaf commented Sep 13, 2014

Are you by any chance using CyanogenMod and did enable whisperpush?

@Wopfi
Copy link

Wopfi commented Sep 13, 2014

You're right! I actually had WhisperPush enabled. Don't know when or why I did this thou.

@Wopfi
Copy link

Wopfi commented Sep 21, 2014

And now, sending SMSes manually works. But why did WhisperPush interfere with sending normal SMSes. My friend wasn't using CyanogenMod and never registered for WhisperPush.

@rhodey rhodey closed this as completed Mar 16, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

7 participants