Closed Bug 834728 Opened 12 years ago Closed 11 years ago

[EMAIL] opening the Email app seems to also trigger the Calendar app to be opened

Categories

(Firefox OS Graveyard :: Gaia::E-Mail, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: maat, Unassigned)

Details

(Whiteboard: interaction [UX-P1], [TEF_REQ])

**DESCRIPTION** opening the Email app seems to also trigger the Calendar app to be opened **PATH** 1) ensure all apps are closed 2) open the email app 3) use the app (e.g.) navigate its folders, refresh inbox, send an email 4) long press the home button on the phone **EXPECTED** view of thumbnails illustrating open apps appears showing just the Email app open **ACTUAL** view of thumbnails illustrating open apps appears showing the Email app AND the Calendar app open. ..and no the calendar has no content for today. [TEF_REQ] as Feature required for TEF build.
Whiteboard: interaction [UX-P1], [TEF_REQ]
just as a further to this, as and F.Y.I. it would seem to me that it is the act of sending an email that is triggering the Calendar app to open.
I'm not seeing this on a recent build when using the e-mail app or sending e-mails. Based on this and other bugs you have filed today, I think you may be running an older build of Gaia where I think the calendar synchronization logic was broken so it was constantly using the mozAlarms API to open itself up to synchronize. Please provide the build info from where you can repro this, and if it's an older build please try to reproduce on a recent build before reopening. I think a v1.0.0 build should be fine.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
I think it's due to the transparency bug which is fixed: bug 822721
I read Ayman's bug as calendar magically shows up in the background somehow, which is what I saw during most of the work week and shortly after. The transparency bug shows you the calendar app opening because the homescreen accidentally ended up seeing the click event.
> Please provide the build info from where you can repro this, The Build ID I first saw this on was: 20130123095911. I sent you the Log Cat via email. I am still experiencing it tonight (Berlin time) with Build ID: 20130124144638 so i am going to reopen this bug.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Do you have any remote calendars configured? If so, what is your calendar synchronization interval set to? If it's not "manually", you might want to try setting it to that. Also, I guess make sure you don't have any upcoming events that want to fire. logcat had nothing related to any app launches, just some e-mail stuff. As noted elsewhere, I think the logcat circular buffer had probably overflowed during testing, so there could be a lot of things that were lost.
(In reply to Andrew Sutherland (:asuth) from comment #6) > Do you have any remote calendars configured? No. no remote calendars are configured > Also, I guess make sure you don't have any upcoming > events that want to fire. There are no events recorded in the calendar app. Its in a 'venilla state' as it has not been used since i last reset the phone.
James, any thoughts on what could cause Calendar to pop-up in the background on recent builds?
Flags: needinfo?(jlal)
Andrew, the Calendar app is located where the address drawer and back button is located. The transparency bug is in regards to at certain transitions, the homescreen will take the touch event. If the transition is happening and the homescreen gets the touch, the calendar app will open but the animations will cause the email app remain at the top. I still believe it's an instance of bug 822721
Which I am not convinced is fully fixed.
Sorry for the lag... there is a bug when you open up calendar we create the alarm schedule to sync even with an offline account (https://bugzilla.mozilla.org/show_bug.cgi?id=821604). So when you open calendar we sync... There is an almost complete patch there but it needs rebasing and a little love (tests).
Flags: needinfo?(jlal)
Per James Lal, this was probably bug 821604. Failing that, it's possible it was bug 822721. Not sure a dupe adds anything given the bug, so marking invalid.
Status: REOPENED → RESOLVED
Closed: 12 years ago11 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.