Closed Bug 1000496 Opened 5 years ago Closed 5 years ago

[B2G][Clock]Deleting an alarm then killing the clock app and relaunching it causes the deleted alarm to reappear

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set

Tracking

(b2g-v1.4 unaffected, b2g-v2.0 fixed)

VERIFIED FIXED
1.4 S6 (25apr)
Tracking Status
b2g-v1.4 --- unaffected
b2g-v2.0 --- fixed

People

(Reporter: astole, Assigned: mcav)

References

()

Details

(Keywords: regression, Whiteboard: [p=1])

Attachments

(2 files)

13.53 KB, text/plain
Details
46 bytes, text/x-github-pull-request
mmedeiros
: review+
Details | Review
Attached file logcat
When an alarm is deleted, it will reappear if the clock app is killed then relaunched. If the Clock app is not killed, the alarm will stay deleted.

Repro Steps:
1) Update a Open_C to BuildID: 20140423040203
2) Launch the Clock app
3) Create a new alarm
4) Kill the Clock app by long pressing the home button
5) Relaunch the Clock app

Actual:
The alarm reappears when relaunching the Clock app

Expected:
The deleted alarm stays deleted

2.0 Environmental Variables:
Device: Open_C 2.0
BuildID: 20140423040203
Gaia: d8904c5af6152f5d647a93a0c31227171ddecd87
Gecko: ac376a4e8174
Version: 31.0a1
Firmware Version: P821A10-ENG_20140410

Repro frequency: 100%
See attached: Video, logcat
Leaving qawanted to check 1.4.
Keywords: qawanted
This issue also occurs on the latest Buri 2.0.

2.0 Environmental Variables:
Device: Buri 2.0 MOZ
BuildID: 20140423040203
Gaia: d8904c5af6152f5d647a93a0c31227171ddecd87
Gecko: ac376a4e8174
Version: 31.0a1
Firmware Version: V1.2-device.cfg

This issue does not occur on the latest 1.4.

1.4 Environmental Variables:
Device: Open_C 1.4
BuildID: 20140423000203
Gaia: b6a41ee9e2934fe9692da6fb1cb310cb759e9870
Gecko: 2d1b4d36eef9
Version: 30.0a2
Firmware Version: P821A10-ENG_20140410
The STR on the bug here is wrong - it's not talking about deleting an alarm. Can you fix it?
Flags: needinfo?(astole)
Moving to qawanted to resolve comment 3.
Sorry about that. Updated STR:

Repro Steps:
1) Update a Open_C to BuildID: 20140423040203
2) Launch the Clock app
3) Create a new alarm
4) Delete alarm
5) Kill the Clock app by long pressing the home button
6) Relaunch the Clock app

Resolving comment 3 so removing qawanted and adding regressionwindow-wanted
Flags: needinfo?(astole)
blocking-b2g: --- → 2.0?
Assignee: nobody → m
Status: NEW → ASSIGNED
Target Milestone: --- → 1.4 S6 (25apr)
Attached file Pull Request
Apparently throwing an error in an IndexedDB request's 'onsuccess' handler causes the transaction to not actually complete. Not sure why this is just showing up now.
Attachment #8411425 - Flags: review?(mmedeiros)
Comment on attachment 8411425 [details] [review]
Pull Request

LGTM, nice work!
Attachment #8411425 - Flags: review?(mmedeiros) → review+
thanks!

landed: https://github.com/mozilla-b2g/gaia/commit/acde8c692e69a7caf00d1200f16311cb3e4e722a
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
blocking-b2g: 2.0? → ---
[Environment]
Gaia      d23e479e8a4ce0bc620acb2d7e2f82801aa4d0ea
Gecko     https://hg.mozilla.org/releases/mozilla-aurora/rev/36f67ce46855
BuildID   20140427000203
Version   30.0a2
ro.build.version.incremental=324
ro.build.date=Thu Dec 19 14:04:55 CST 2013


[Result]
PASS
Status: RESOLVED → VERIFIED
Whiteboard: [p=1]
You need to log in before you can comment on or make changes to this bug.