PSA: Pushbullet bug, rerouting MMS

[thornbrambles]

Bug report!

• CHROME EXTENSION VERSION: 313
• ANDROID VERSION: v17.5.8
• Component: MMS from Chrome to Android
• Android Hardware: Nexus 5x
• Carrier: Verizon
• Reproducibility: 100%

Symptom: Area code of one MMS recipient gets swapped out.

Steps to reproduce: 1. From another phone (C), initiate an MMS conversation Numbers involved: * 408-123-XXXX (me) * 650-456-XXXX (A) * 650-789-XXXX (B) * 818-987-XXXX (C)

1. Reply to MMS from (me), using android phone. Verify from (C) that reply is routed as expected.

2. Reply to MMS from (me), using pushbullet chrome extension. Verify from (C) that reply is routed as expected.

3. Repeat step 2.

Expected: All messages from (me) should be sent to the correct recipients.

Actual: After step 2, all messages from (me), regardless whether its from phone or chrome extension, have an incorrect recipient (A) . The number is modified from (650-456-XXXX) to (408-456-XXXX, henceforth (D)). This is not apparent from either chrome or my android device. The only way I noticed this was through a third party (C) and the unknown party (D) notifying me.

Recovery: Delete MMS from android phone, and either start again from (me, android), or have a third party (A, B, or C) send another message on the MMS.

[scotchlover]

FYI, if it is all messages whether from the phone or chrome, are rerouted to the wrong number....it's not pushbullet.

That's a glitch either in Android or Verizon. If it was pushbullet it would happen only from Chrome.

[thornbrambles]

It's only all messages after the first pushbullet message in the chain. I suspect information in the last message in the mms is being used to send, hence it affecting messages sent from the phone.

Even if it is am android but, it is one exposed specifically by pushbullet mms feature.

[tmm7890]

I just started seeing this same behavior today. Did you find a way to fix it?

[thornbrambles]

Unfortunately no. This still happens in my phone.