Closed
Bug 1188663
Opened 9 years ago
Closed 9 years ago
[Calender] Event reminder does not trigger notification.
Categories
(Firefox OS Graveyard :: Gaia::Calendar, defect)
Tracking
(b2g-v2.2 affected, b2g-master affected)
RESOLVED
DUPLICATE
of bug 1032101
People
(Reporter: NicholasN, Unassigned, NeedInfo)
References
()
Details
(Keywords: regression, Whiteboard: [2.5-Daily-Testing][Spark])
Attachments
(1 file)
(deleted),
text/plain
|
Details |
Description:
The user adds a new offline event starting 6 minutes in the future, and sets the Remind me field to 5 minutes before. They save the event and close the calendar app. They wait on the home screen for one minute, and the reminder does not trigger a notification.
Repro Steps:
1) Update a Aries to 20150727151800
2) Go to Calendar and add a new event.
3) Set the day to the current day, and the time starting 6 minutes in the future.
4) Set the Remind me field to 5 minutes before.
5) Save the event and close the app.
6) Wait on the homescreen for at least one minute.
Actual:
Calendar event reminder does not trigger a notification.
Expected:
Reminder triggers notification.
Notes:
Environmental Variables:
Device: Aries 2.5
Build ID: 20150727151800
Gaia: 4e3e21a4ba3f188b45623ee2297f21d0791f8667
Gecko: 21ca97268bae
Gonk: 2916e2368074b5383c80bf5a0fba3fc83ba310bd
Version: 42.0a1 (2.5)
Firmware Version: D5803_23.1.A.1.28_NCB.ftf
User Agent: Mozilla/5.0 (Mobile; rv:42.0) Gecko/42.0 Firefox/42.0
Repro frequency: (4/4)
See attached: video clip, logcat
Reporter | ||
Comment 1•9 years ago
|
||
Issue also occurs on Flame 2.5 and Flame 2.2, but not Flame 2.1
Flame 2.5
Actual Result:
Calendar event reminder does not trigger a notification.
Environmental Variables:
Device: Flame 2.5
BuildID: 20150728030208
Gaia: 14e32276025b0310d3e89027320cf4b2a24cedfb
Gecko: 33dc8a83cfc0
Gonk: 41d3e221039d1c4486fc13ff26793a7a39226423
Version: 42.0a1 (2.5)
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:42.0) Gecko/42.0 Firefox/42.0
Flame 2.2
Actual Result:
Calendar event reminder does not trigger a notification.
Environmental Variables:
Device: Flame 2.2
BuildID: 20150728032504
Gaia: e1e6317f17a840b19af9dbb25f5a771d8d9fa161
Gecko: 9b60e57724db
Gonk: bd9cb3af2a0354577a6903917bc826489050b40d
Version: 37.0 (2.2)
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0
Flame 2.1
Actual Result:
Calendar reminder triggers a notification.
Environmental Variables:
Device: Flame 2.1
BuildID: 20150724001207
Gaia: 9dba58d18006e921546cec62c76074ce81e16518
Gecko: 41e10c6740be
Gonk: bd9cb3af2a0354577a6903917bc826489050b40d
Version: 34.0 (2.1)
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
QA Whiteboard: [QAnalyst-Triage?]
status-b2g-v2.2:
--- → affected
status-b2g-master:
--- → affected
Flags: needinfo?(pbylenga)
Keywords: regression
Whiteboard: [2.5-Daily-Testing][Spark]
Comment 2•9 years ago
|
||
[Blocking Requested - why for this release]:
Functional regression (not firing event reminders)
Requesting a window.
blocking-b2g: --- → 2.5?
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(pbylenga)
Keywords: regressionwindow-wanted
Updated•9 years ago
|
QA Contact: jmercado
Comment 3•9 years ago
|
||
This issue actually seems to be related to the clock being off. I am having trouble locating the bug but there is already an issue written up where the clock will display hours off from the actual time. You can tell this issue when setting up the event because the event will default to starting at the beginning of the next hour (setting up an event at 1:30 PM will default to 2:00 PM start time) which will be wildly different than what would be expected based on the clock in the status bar.
In tests today, my phone was displaying in the status bar that the time was 6 PM and if I created events based on that I would not receive notifications, but if I created them based on the actual time, the notifications would occur as expected.
Environmental Variables:
Device: Aries 2.5
BuildID: 20150729013848
Gaia: 21256d7665f972255d198f8af81a8df4bd0e0fc4
Gecko: 2ee9895e032c
Gonk: 2916e2368074b5383c80bf5a0fba3fc83ba310bd
Version: 42.0a1 (2.5)
Firmware Version: D5803_23.1.A.1.28_NCB.ftf
User Agent: Mozilla/5.0 (Mobile; rv:42.0) Gecko/42.0 Firefox/42.0
Environmental Variables:
Device: Flame 2.5
BuildID: 20150729030209
Gaia: 21256d7665f972255d198f8af81a8df4bd0e0fc4
Gecko: 2ee9895e032c
Gonk: 41d3e221039d1c4486fc13ff26793a7a39226423
Version: 42.0a1 (2.5)
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:42.0) Gecko/42.0 Firefox/42.0
Flags: needinfo?(ktucker)
Comment 4•9 years ago
|
||
I'll check to see if I can reproduce.
Updated•9 years ago
|
Flags: needinfo?(gaye)
Comment 5•9 years ago
|
||
this might be related to https://bugzilla.mozilla.org/show_bug.cgi?id=1120850#c6
Comment 6•9 years ago
|
||
This is actually caused by the time being incorrect. Please see bug 1032101
Status: NEW → RESOLVED
blocking-b2g: 2.5? → ---
Closed: 9 years ago
QA Whiteboard: [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
Keywords: regressionwindow-wanted
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•