Alarm-Clock Fails to Remove Deprecated Alarm after Resetting It with a New Time

RESOLVED FIXED

Status

()

Core
General
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: Gene Lian (I already quit Mozilla), Assigned: iliu@mozilla.com, ianliu.moz@gmail.com)

Tracking

Trunk
ARM
Gonk (Firefox OS)
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

5 years ago
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.
(Reporter)

Comment 1

5 years ago
Hi Ian,

Directly assigning this to you if you don't mind. ;)
Assignee: nobody → iliu
Hi Gene,
Thank you to find out the wrong logic to set an existed alarm.
I'll take over the issue.
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.
(Assignee)

Updated

5 years ago
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.