982150 - [B2G][SMS] An SMS is not displayed after hit "Send". The user is unable to open and view any of the sent or received SMSs from the messages list.

Status: VERIFIED FIXED

(Firefox OS Graveyard :: Gaia::SMS, defect)

Description

[Natalya Kot [:nkot]]

Attachment: logcat

Description:
An SMS is not displayed in the thread after hit "Send".The user is unable to open and view it from the messages list. Unable to open and view any of the received messages as well. 

Repro Steps:
1) Updated Buri to BuildID: 20140311040203
2) Open Messages
3) Enter valid number
4) Enter message --> Send
5) Tap "<" to go back to messages list
6) Tap the number to open thread

Actual:
- The messages is not displayed in the thread after hit "Send"
- Tapping the number in the messages list won't open thread 

Expected:
An SMS is displayed to the user once sent
The user is able to open and view sent/received SMSs from the messages list

Environmental Variables:
Device: Buri master (v1.4) Mozilla RIL
BuildID: 20140311040203
Gaia: a351fe62c11737c722ad33aaff438f6ccd00bd4a
Gecko: 41d962d23e81
Version: 30.0a1
Firmware Version: v1.2-devices.cfg

Notes: 
Rebooting device or resetting doesn't resolve the issue. 

Repro frequency: 100%, 3/3 devices
See attached logcat

Comment 1

[Marcia Knous [:marcia]]

Adding qaurgent so we can nail down a regression window on this one.

Comment 2

[Natalya Kot [:nkot]]

It appears that the issue only happens with SMSs to/from non-contact (just a number). When sending an SMS to a saved contact the user is able to see their message and also able to open it from the Messages app.

Comment 3

[Natalya Kot [:nkot]]

Also, there are no SMS notifications when receive messages from non-contact number.

Comment 4

[Julien Wajsberg [:julienw] (PTO -> Mar 16)]

Could be bug 974733 that I landed this morning on central.
(didn't try to reproduce yet)

Feel free to backout if this proves to be the source of the issue.

Comment 5

[Brogan Zumwalt [Inactive]]

- Last Working -
Device: Buri ENG v1.4 MOZ RIL
BuildID: 20140310060628
Gaia: 8280f6749b8183e4bc52ce84affca310858e86d2
Gecko: 06162d3f18ab
Version: 30.0a1
Firmware Version: V1.2-device.cfg

- First Broken -
Device: Buri ENG v1.4 MOZ RIL
BuildID: 20140310075126
Gaia: 3aff60a128e57b286e13b89c6bcb8fa43ed81836
Gecko: 08aec9942990
Version: 30.0a1
Firmware Version: V1.2-device.cfg

Last working Gaia/First broken Gecko: Issue Does NOT Reproduce
Gaia: 8c9191df3c107df4073f3ca63816a1d36c51af5d
Gecko: 41d962d23e81

First broken Gaia/Last working Gecko: Issue DOES Reproduce
Gaia: 6fbeac2415f07f10de181f0877ddf67ee299b885
Gecko: 923f1411f42f

Push log: https://github.com/mozilla-b2g/gaia/compare/8280f6749b8183e4bc52ce84affca310858e86d2...3aff60a128e57b286e13b89c6bcb8fa43ed81836

Comment 6

[Julien Wajsberg [:julienw] (PTO -> Mar 16)]

ok, 2 culprits:
* bug 981327
* bug 921971

The first one seems more related.

Bug 974733 should be fine then.

Comment 7

[Julien Wajsberg [:julienw] (PTO -> Mar 16)]

Won't be able to investigate more as I need to leave, sorry.

Comment 8

[Jason Smith [:jsmith]]

The logcat doesn't have console enabled. Can we get a logcat with console enabled? I'm expecting something really obvious to jump out there.

Comment 9

[Natalya Kot [:nkot]]

Attachment: logcat_console_enabled

Comment 10

[Natalya Kot [:nkot]]

Attachment: logcat_one_more

Comment 11

[Jason Smith [:jsmith]]

03-11 11:57:11.869: E/GeckoConsole(898): [JavaScript Error: "TypeError: result is null" {file: "app://sms.gaiamobile.org/gaia_build_defer_index.js" line: 824}]
03-11 11:57:12.689: E/GeckoConsole(136): [JavaScript Error: "IndexedDB UnknownErr: IDBTransaction.cpp:863"]

Comment 12

[Jason Smith [:jsmith]]

Mike dug into this a bit - looks like bug 981327 is definitely the cause. He's going to back out that patch in a little bit.

Comment 13

[Michael Henretty [:mikehenrty][:mhenretty]]

Github is having issues right now, but I will back out as soon as it's stable again:

https://status.github.com/

Comment 14

[Michael Henretty [:mikehenrty][:mhenretty]]

Reverted: https://github.com/mozilla-b2g/gaia/commit/2dd9e509aeec0cb01bee17f42494b0a501128792

Comment 15

[Julien Wajsberg [:julienw] (PTO -> Mar 16)]

Thanks Jason and Michael.

Note that I see the IndexedDB error line in working builds as well, but it's difficult to know where it comes from :(

Comment 16

[Natalya Kot [:nkot]]

Still seeing this issue in today's master build, but looks like this is not the latest Gaia... 
BuildID: 20140312040203
Gaia: 3005269d4dcabcc7d27eaf72bda44a969873af8c
Gecko: 23005b395ae8
Version: 30.0a1

We pulled the latest Gaia and retested and the issue doesn't reproduce
BuildID: 20140312040203
Gaia: c22466e71c6da1d472ce28733a001fae37bcdc5e
Gecko: 23005b395ae8
Version: 30.0a1

Comment 17

[Julien Wajsberg [:julienw] (PTO -> Mar 16)]

Yep, Gaia 3005269d4dcabcc7d27eaf72bda44a969873af8c is older than the fix :)

Comment 18

[Natalya Kot [:nkot]]

Verified Fixed.
Works now :)

BuildID: 20140313131233
Gaia: ea9e23abea5933656555d849b922c8da7530c90b
Gecko: fe40387eba1a
Version: 30.0a1
v1.2-device.cfg