[B2G][Gaia][Calendar] Calendar events do not save correctly when gcal is toggled off and app is closed then reopened

NEW
Unassigned

Status

Firefox OS
Gaia::Calendar
3 years ago
3 years ago

People

(Reporter: ddixon, Unassigned)

Tracking

unspecified
x86
Gonk (Firefox OS)

Firefox Tracking Flags

(b2g-v1.3 affected, b2g-v1.4 affected, b2g-v2.0 affected, b2g-v2.1 affected)

Details

Attachments

(1 attachment)

(Reporter)

Description

3 years ago
Created attachment 8459889 [details]
Calendar events logcat

Description:
Offline calendar events do not save properly when user activates but unchecks the gcal (google calendar).  Created calendar events are not saved after creating them, closing, and reopening the app. 


Repro Steps:
1) Update a Flame to 20140721055837
2) Open Calendar App and sign into personal gcal account
3) Toggle off gcal and return to calendar
4) Create events then close and reopen calendar app


Actual:
Offline calendar events do not save after closing an reopening Calendar app.  

Expected:
All created calendar events save correctly. 

Environmental Variables:
Device: Flame Master
Build ID: 20140721055837
Gaia: Unknown
Gecko: 0dc711216018
Version: 33.0a1 (Master)
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0


Keywords: calendar, created events

This issue is possibly related to or could be a duplicate of the following: 

https://bugzilla.mozilla.org/show_bug.cgi?id=823659
https://bugzilla.mozilla.org/show_bug.cgi?id=982240
https://bugzilla.mozilla.org/show_bug.cgi?id=986734
https://bugzilla.mozilla.org/show_bug.cgi?id=1016687
https://bugzilla.mozilla.org/show_bug.cgi?id=1009210

Repro frequency: 9/10 90%

See attached: logcat
(Reporter)

Comment 1

3 years ago
DOES occur on Flame 2.1, 2.0, 1.4, 1.3, Buri 2.1 


Device: Flame Master
Build ID: 20140721055837
Gaia: Unknown
Gecko: 0dc711216018
Version: 33.0a1 (Master)
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0

Device: Flame 2.0
Build ID: 20140721082721
Gaia: b9d19011123487009c80d1200937652d58c434a0
Gecko: d69cd84b6824
Version: 32.0a2 (2.0)
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Device: Flame 1.4 (created event does not appear at all)
Build ID: 20140716000202
Gaia: 393d72937727ad20e82b2ff7b13e3d7ff077a9f0
Gecko: 932c37978d37
Version: 30.0 (1.4)
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0

Device: Flame 1.3 (created event does not appear at all)
Build ID: 20140616171114
Gaia: e1b7152715072d27e0880cdc6b637f82fa42bf4e
Gecko: e181a36ebafaa24e5390db9f597313406edfc794
Version: 28.0 (1.3)
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:28.0) Gecko/28.0 Firefox/28.0

Device: Buri Master
Build ID: 20140721142028
Gaia: 649245c238a043af32acb109b2613f578323f8e1
Gecko: 5b64c42742cd
Version: 34.0a1 (Master)
Firmware Version: v1.2device.cfg
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
(Reporter)

Updated

3 years ago
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmitchell)
not a regression
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
status-b2g-v1.3: --- → affected
status-b2g-v1.4: --- → affected
status-b2g-v2.0: --- → affected
status-b2g-v2.1: --- → affected
Flags: needinfo?(jmitchell)

Updated

3 years ago
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage+][lead-review+]

Comment 3

3 years ago
It appears that in this case, the created event is now stored on Google calender rather than the offline one.

Comment 4

3 years ago
Never mind, I was doing it wrong
You need to log in before you can comment on or make changes to this bug.