Closed Bug 983837 Opened 6 years ago Closed 6 years ago

[B2G][Clock]Unable to delete an Alarm

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set

Tracking

(blocking-b2g:1.4+, b2g-v1.4 fixed)

VERIFIED FIXED
1.4 S3 (14mar)
blocking-b2g 1.4+
Tracking Status
b2g-v1.4 --- fixed

People

(Reporter: astole, Unassigned)

References

Details

(Keywords: regression, smoketest)

Attachments

(1 file)

Attached file logcat
After creating an alarm, the user is unable to delete it or change the snooze option. Also, on some occasions, attempting to edit the different alarm options brings the user to the Timer or Stopwatch menu.

Repro Steps:
1) Update a Buri to BuildID: 20140314093423
2) Open Clock app
3) Create a new alarm
4) Open newly created alarm and attempt to delete it

Actual:
User is unable to delete the alarm

Expected:
The user can delete created alarms

1.4 Environmental Variables:
Device: Buri 1.4 MOZ
BuildID: 20140314093423
Gaia: 1cef557f9e9a865d1bf49d99a8f1cca1f0f4f5c4
Gecko: 142911d6d987
Version: 30.0a1
Firmware Version: v1.2-device.cfg

Repro frequency: 100%
See attached: logcat
QA Contact: bzumwalt
Keywords: qaurgent
Also fixed by backout of the blocking bug here.
Blocks: 968483
Status: NEW → RESOLVED
blocking-b2g: --- → 1.4+
Closed: 6 years ago
Resolution: --- → FIXED
I am able to delete alarms that I've created in the Clock app on the latest Buri 1.4 build. 

Environmental Variables:
Device: Buri Master M-C mozRIL
BuildID: 20140317040204
Gaia: 8f802237927c7d5e024fb7dca054dd5efef6b2e6
Gecko: 25cfa01ba054
Version: 30.0a1
v1.2-device.cfg
Status: RESOLVED → VERIFIED
Target Milestone: --- → 1.4 S3 (14mar)
You need to log in before you can comment on or make changes to this bug.