Closed Bug 963452 Opened 10 years ago Closed 10 years ago

[1.3][OMA CP] Open CP message but no message shows.

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(blocking-b2g:1.3+)

RESOLVED WORKSFORME
blocking-b2g 1.3+

People

(Reporter: echu, Unassigned)

Details

Attachments

(4 files)

After bug 934354 is fixed, with special steps that message will not show after open it.

1. Send a CP message to DUT, open it.
2. Press power key to turn off display, notification will pop up and wake up device(due to bug 934354 solution).
3. Unlock it, and wait for notification disappear, drag down notification bar and tap the message.
4. Once message is opened, press power key to turn off display. Notification will pop up and wake up device.
5. Unlock it, and wait for notification disappear, drag down notification bar and tap the message. No message will be shown.

Buri
Gaia      6fbeac2415f07f10de181f0877ddf67ee299b885
Gecko     http://hg.mozilla.org/releases/mozilla-aurora/rev/e8f6bdf8db3d
BuildID   20140123004001
Version   28.0a2

100% reproducible.
It seems that sometimes it's easily hit the problem even when first time opening the message or suspend device once. Original reproduce steps can still hit the problem as well, but just attach more log and videos indicates this bugs can easily be seen not just for one type of steps.
Nominate 1.3? since sometimes even just open the message for first time, nothing shows.
blocking-b2g: --- → 1.3?
At 4., I suppose you send a second message to the device ?
(In reply to Julien Wajsberg [:julienw] from comment #5)
> At 4., I suppose you send a second message to the device ?

No, it's the new feature from bug 934354. If user doesn't apply the setting and does not exit it from normal process, the message will be kept but in the way like a new incoming notification, but the description will become "Configuration message not processed...".

(Normal exit CP message process: press "x" icon on the left, a new confirmation window pops up asking user whether he/she wants to exit or not)
Oh sorry, it was about wappush, I thought it was SMS...
(In reply to Enpei from comment #0)

> 1. Send a CP message to DUT, open it.
> 2. Press power key to turn off display, notification will pop up and wake up
> device(due to bug 934354 solution).
> 3. Unlock it, and wait for notification disappear, drag down notification
> bar and tap the message.
> 4. Once message is opened, press power key to turn off display. Notification
> will pop up and wake up device.
> 5. Unlock it, and wait for notification disappear, drag down notification
> bar and tap the message. No message will be shown.

That's weird. I did similar test when working on bug 934354 and it was working well. I'll try to reproduce the issue with the build below. I tested on peak device but I don't think that matters.

> Buri
> Gaia      6fbeac2415f07f10de181f0877ddf67ee299b885
> Gecko     http://hg.mozilla.org/releases/mozilla-aurora/rev/e8f6bdf8db3d
> BuildID   20140123004001
> Version   28.0a2
Component: Gaia::System → Gaia::Wappush
Hardware: x86_64 → ARM
I'm not able to reproduce this issue with latest v1.3 build (buri device). See below the build info. Check out the video with the test at http://youtu.be/M7k_Esvk_ao

Enpei, could you give a try with the latest v1.3 build please? Thanks.

Gecko 8d902e182f8138c264df6fb1f6db1250b54c874a
Gaia b0aa74619cffb7a39ee0e7da5e9361a98e69f3f6
Version=28.0a2
Keywords: qawanted
See comment #9 please.
Flags: needinfo?(echu)
blocking-b2g: 1.3? → 1.3+
After I ran WAP Push test cases, I've seen this issue a few times on 1.3 MOZ RIL build
But it wasn't 100% reproducible. The CP message just disappears when tapping a message to open

Device: Buri 1.3 MOZ
BuildID: 20140127004002
Gaia: 25a45a836a4a21a30f63fa7b544b42e8b781180a
Gecko: c40099a42c1f
Version: 28.0a2
Firmware Version: v1.2-device.cfg
Keywords: qawanted
Flags: needinfo?(echu)
(In reply to sarsenyev from comment #11)
> After I ran WAP Push test cases, I've seen this issue a few times on 1.3 MOZ
> RIL build
> But it wasn't 100% reproducible. The CP message just disappears when tapping
> a message to open

As I commented in comment #10 I'm not able to reproduce the issue (see the video in the comment please). How did you run the test cases? Is there any special condition you might comment?, How do you send the messages? FYI I use the same server used in the IOT.
Flags: needinfo?(sarsenyev)
(In reply to Enpei from comment #2)
> Created attachment 8364899 [details]
> 14:15, first time open message but no content shows.

In the attached video I see the message being showed is not one of the you previously quit since the description in the notification is not 'Configuration message not processed yet'.

(In reply to Enpei from comment #1)
> Created attachment 8364898 [details]
> time stamp: 14:45, 14:49.

During this test It seems you sent multiple messages to the device and it's quite confusing when trying to find any issue.

Could you provide the STR, logs and a video reproducing the issue by sending only one message and quitting, waiting for the notification again, re-opening the message and so on please? Thanks!

PS: Since Enpei might be PTO, sarsenyev, could you provide them? Thanks
Flags: needinfo?(echu)
During the test run, I am confirming that I've seen this this issue on 1.3 a few times
But I cannot provide steps or video or logs, because it's very intermittent
Flags: needinfo?(sarsenyev)
I(In reply to sarsenyev from comment #14)
> During the test run, I am confirming that I've seen this this issue on 1.3 a
> few times
> But I cannot provide steps or video or logs, because it's very intermittent

Well I don't know how to continue then. Jason, since I'm not able to reproduce the issue, have attached a video showing that It works, and there is not STR (I'm not able to reproduce the issue by following the STR at comment #0), logs showing up any error, or even videos, how is this situation supposed to be handled? I'm tempted to resolve this bug as WORKSFORME but your feedback is more than welcome. Thanks.
Flags: needinfo?(jsmith)
I think the best course of action is to wait for Enpei to come back on the needinfo request. CNY is almost over, so she should be able to reply to this soon. She's also the lead on this feature, so she should be able to provide guidance on how to move forward here with this bug in terms of it's reproducibility.
Flags: needinfo?(jsmith)
In reply to José Antonio Olivera Ortega [:jaoo] from comment #13)
> (In reply to Enpei from comment #2)
> > Created attachment 8364899 [details]
> > 14:15, first time open message but no content shows.
> 
> In the attached video I see the message being showed is not one of the you
> previously quit since the description in the notification is not
> 'Configuration message not processed yet'.
Please ignore the statement that I might attach the wrong video. I did meet the problem when I first time open the message.
> 
> (In reply to Enpei from comment #1)
> > Created attachment 8364898 [details]
> > time stamp: 14:45, 14:49.
> 
> During this test It seems you sent multiple messages to the device and it's
> quite confusing when trying to find any issue.
> 
> Could you provide the STR, logs and a video reproducing the issue by sending
> only one message and quitting, waiting for the notification again,
> re-opening the message and so on please? Thanks!

I already provided the STR I did at that time. At 14:45 in the video, from the log what has happened when I tapped the message and nothing came out? 

I did send multiple message during the test but only one after one, not sent them all at the same time. I only sent the next one when I reproduced the issue, which means after open a message but nothing comes out, I send another to DUT.
Flags: needinfo?(echu)
(In reply to Enpei from comment #17)
> I already provided the STR I did at that time. At 14:45 in the video, from
> the log what has happened when I tapped the message and nothing came out? 

The error I see is (even multiple times):

01-24 14:48:00.129 E/GeckoConsole(  136): [JavaScript Error: "TypeError: this._resetTouchStates is not a function" {file: "app://system.gaiamobile.org/shared/js/lockscreen_slide.js" line: 238}]

But I don't know this is causing the issue.
I'm not able to reproduce the issue. I'm sorry I cannot spend more time on this. I would suggest to test with a recent build as you guys were able to reproduce it and provide the STR.

(In reply to Enpei from comment #17)

> > Could you provide the STR, logs and a video reproducing the issue by sending
> > only one message and quitting, waiting for the notification again,
> > re-opening the message and so on please? Thanks!
> 
> I already provided the STR I did at that time. At 14:45 in the video, from
> the log what has happened when I tapped the message and nothing came out? 

Everything seems correct and nothing like an error is showing up.
Okay - given the exhaustion on effort here, I'm going to close this as incomplete.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → INCOMPLETE
Hi all,

I've tried to verify the bug on latest 1.3 build with either first time opening CP message or original reproduce steps for 20 times, not able to reproduce it. Works for me now.

Gaia      f9a37c77efb4621a1f57e4695b497d18601fe134
Gecko     http://hg.mozilla.org/releases/mozilla-aurora/rev/3d9d920ca43b
BuildID   20140203004001
Version   28.0a2
Resolution: INCOMPLETE → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: