Closed Bug 798718 Opened 13 years ago Closed 12 years ago

[Email] Tapping new email notification does not launch Email App

Categories

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

ARM
Gonk (Firefox OS)
defect

Tracking

(blocking-basecamp:-)

RESOLVED INVALID
blocking-basecamp -

People

(Reporter: tchung, Unassigned)

References

Details

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

When a new mail notification arrives, tapping the notification in the notifications bar does not launch the Email App. Environment: - 10/5 daily otoro build - gaia: ca1f327d5acc198bb4be62fa51db2c039032c9ce - gecko: ddc8eeb3f9b9ee04d9f74b4f60522eb4530a4a6f Repro: 1) setup email and add an account (gmail) 2) From another account, send a test email to that account 3) have email notifications set. watch a notification mail from that account get sent through the notifications bar. 4) click the email notification 5) Verify the notification count decreases by 1, but the email app is not launched and you cant see your message. Expected: - clicking the notification should launch the Email app to view the newly arrived email. Actual: - tapping the email notification only decrements the count, and never launches the email app.
Is there any adb log for this? I had a hard time testing this because b2g-desktop was being very crashy if I tried to change apps, but I did notice some XPCOM-looking errors in the output when we would call launch() on our app.
Leaving a trace for next triage sessions: Looks like this is *not* related to https://bugzilla.mozilla.org/show_bug.cgi?id=755402
blocking-basecamp: ? → +
Hi Tony, I've tested this issue on device today and email app could be launched via notification bar. Could you please verify it again? Thanks. Environment: - gaia: 8258c8302507787d57d441068c09f77197765fc4 - gecko: c96b188e4b7d480bdd897eb7b368afc91b8e6e5f
Re-nominating -- no longer blocking+. Per discussion with Chris Lee we are dropping email notifications from v1.
blocking-basecamp: + → ?
blocking-basecamp: ? → -
I'm on daily build 10/25, and I can still reproduce this (re: comment #3).
Priority: -- → P5
Whiteboard: v2, interaction
just updating whiteboard with Josh's UX P5 priority
Whiteboard: v2, interaction → v2, interaction [UX-P5]
[UX-P1], [TEF_REQ] as Feature required for TEF build.
Whiteboard: v2, interaction [UX-P5] → v2, interaction [UX-P1], [TEF_REQ]
Blocks: 834664
We do not have any email notifications. Hence, this bug does not apply anymore, and it should be closed.
Whiteboard: v2, interaction [UX-P1], [TEF_REQ] → v2, interaction [UX-P1], [TEF_REQ], PRODUCT-FEATURE
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.