Last Comment Bug 779059 - Alarm-Clock Fails to Remove Deprecated Alarm after Resetting It with a New Time
: Alarm-Clock Fails to Remove Deprecated Alarm after Resetting It with a New Time
Status: RESOLVED FIXED
:
Product: Core
Classification: Components
Component: General (show other bugs)
: Trunk
: ARM Gonk (Firefox OS)
: -- normal (vote)
: ---
Assigned To: iliu@mozilla.com, ianliu.moz@gmail.com
:
:
Mentors:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-07-31 00:19 PDT by Gene Lian [:gene] (I already quit Mozilla)
Modified: 2012-08-21 20:40 PDT (History)
5 users (show)
See Also:
Crash Signature:
(edit)
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---


Attachments

Description Gene Lian [:gene] (I already quit Mozilla) 2012-07-31 00:19:32 PDT
I discovered this issue when playing around the Alarm-Clock app. There might be something wrong in the Gaia logic. You can replicate this bug by either the following ways:

1. Set an alarm at A time. Reset the same alarm at B time. Delete this alarm. It'll still fire at A time and then crashes the app.

2. Set an alarm at A time. Wait to fire and snooze it. Reset the same alarm at B time. Delete this alarm. It'll still fire at (A + 5min) time and then crashes the app.
Comment 1 Gene Lian [:gene] (I already quit Mozilla) 2012-07-31 00:29:03 PDT
Hi Ian,

Directly assigning this to you if you don't mind. ;)
Comment 2 iliu@mozilla.com, ianliu.moz@gmail.com 2012-07-31 02:51:05 PDT
Hi Gene,
Thank you to find out the wrong logic to set an existed alarm.
I'll take over the issue.
Comment 3 iliu@mozilla.com, ianliu.moz@gmail.com 2012-08-21 20:39:45 PDT
The issue was fixed in Gaia.
Gaia pull request #3497 and landed(https://github.com/mozilla-b2g/gaia/pull/3497).
We can change the status to RESOLVED.

Note You need to log in before you can comment on or make changes to this bug.