1167261 - [Messages][Notification] User will not recieve any indication or notification of a recieved message until the messages app is opened

Status: RESOLVED WORKSFORME

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

Description

[Derek Harris [:DerekH] - Dont need info. Last day 6/5/15]

Description:
Sometimes when the DUT is sent an MMS they will not recieve any indication of the message until the messages app is opened. Only remember this issue occuring when recieving an MMS. Could work with SMS. SIM pin is enabled and could be a factor to this issue. SIM was unlocked when reproducing this issue.


Repro Steps:
1) Update a Flame to 20150521010203
2) Navigate to the homescreen
3) Send an MMS to the DUT
4) Wait about 5mins to ensure the message would be recieved [1]
5) Open Messages app [2]


Actual:
[1] The message is not recieved and no tifiction is given to the user. [2] The message is recieved and there is a notification that the message is recieved only when the app is opened


Expected:
The user recieves notifications of messages recieved by the DUT even without the messages app opened

Environmental Variables:
Device: Flame 3.0 (319mb)(Kitkat)(Full Flash)
Build ID: 20150521010203
Gaia: 5a7f87b1505ba89b586372cbbbe9507d1016c40c
Gecko: b9424d63fe35
Gonk: 040bb1e9ac8a5b6dd756fdd696aa37a8868b5c67
Version: 41.0a1 (3.0)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0


Repro frequency: 3/40
Due to extremely low repro I have been unable to get a logcat or video of this issue


Also unable to confirm whether or not 2.2 is affected

Comment 1

[Derek Harris [:DerekH] - Dont need info. Last day 6/5/15]

QA Wanted to reproduce for branch checks/Logcat, and to find better steps

Comment 2

[Julien Wajsberg [:julienw]]

Do you think this could be bug 1156464 (landed 14th May)? Also note that dependency bug 1162899 landed in v2.2 only today.

Comment 3

[Shine(Leave from Mozilla)]

Attachment: Cannot repro_video.MP4

I cannot reproduce this issue on latest build of Flame 2.0/2.1/2.2/3.0.
I have executed the steps in Comment 0 for 20 attempts with CMCC or CU SIM card inserted in and the SIM PIN is enabled. And I also try to receive the MMS when screen is locked or after killed Messages app from task manager. The received MMS will be noticed on Notification bar. 
See attachment: Cannot repro_video.MP4

Flame 2.0 (319mb) Build ID: 20150522000208
Flame 2.1 (319mb) Build ID: 20150521161204
Flame 2.2 (319mb) Build ID: 20150521162503
Flame 3.0 (319mb) Build ID: 20150521160241

Leaving “qawanted” in case someone else can repro it.

Comment 4

[Jayme Mercado [:JMercado] (Inactive 3/4/2016)]

I was unable to reproduce this issue on today's 3.0 build.  Leaving the tag so someone else can attempt to reproduce.

Environmental Variables:
Device: Flame 3.0
BuildID: 20150526030814
Gaia: 0d67eb545b2f4342525d14e1a10e80c91c87ada0
Gecko: e537a1ba501b
Version: 41.0a1 (3.0) 
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0

Comment 5

[Julien Wajsberg [:julienw]]

From [2] in comment 0 it looks like the system message is correctly sent by the backend, but that the system message subsystem does not deliver to the app for some reason.

Usually the reasons is that the app is opened using another hash (see bug 818000). The only way to open using an hash currently in the SMS app (after bug 1156464 is fixed) is using activities.

Therefore, here is a possible STR I haven't tried:
1. be sure the SMS app is forcibly closed.
2. from the Contacts app, start a SMS with one of the contacts. (alternatively you can choose to "share" a picture from the gallery)
3. press "home" without closing the activity.
4. send a message to the device (SMS or MMS should not give a difference)

Could QA try this?
Thanks !

Comment 6

[KTucker [:KTucker][Inactive 3/4/2016]]

I tried the steps in Comment 5 several times using the contacts app and the gallery app and the dut always received the new "SMS or MMS" notification.

Device: Flame 3.0
BuildID: 20150521010203(Full Flash)(KK)(319mb)
Gaia: 5a7f87b1505ba89b586372cbbbe9507d1016c40c
Gecko: b9424d63fe35
Gonk: 040bb1e9ac8a5b6dd756fdd696aa37a8868b5c67
Version: 41.0a1 (3.0) 
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0

Leaving steps-wanted for others to try.

Comment 7

[Pi Wei Cheng [:piwei] (inactive)]

I also cannot repro. Tried with STR on comment 0 as well as comment 5 multiple times with no reproduction.

Derek, could you try on latest and see if this issue is still reproducible? If not I think we can remove steps-wanted keywords for now until others figure out any kind of valid steps.

Device: Flame (KK, full flashed, 319MB)
BuildID: 20150601010203
Gaia: e6dc0f4c583407a4a52a66ce7cb11f058302a762
Gecko: f8d21278244b
Gonk: 040bb1e9ac8a5b6dd756fdd696aa37a8868b5c67
Version: 41.0a1 (3.0 Master) 
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0

Comment 8

[Derek Harris [:DerekH] - Dont need info. Last day 6/5/15]

I have not been able to reproduce this issue on the latest Flame 3.0 build after many attempts. I think it would be safe to remove the steps wanted keyword from this issue

Environmental Variables:
Device: Flame 3.0 (319mb)(Kitkat)(Full Flash)
Build ID: 20150602055237
Gaia: 6d477a7884273886605049b20f60af5c1583a150
Gecko: 9eae3880b132
Gonk: 040bb1e9ac8a5b6dd756fdd696aa37a8868b5c67
Version: 41.0a1 (3.0)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0