1073543 - [Lockscreen] Actionable notification destination for missed call shows blank blue screen

Status: RESOLVED WORKSFORME

(Firefox OS Graveyard :: Gaia::Dialer, defect, P1)

Description

[Amy Lee [:amylee] UX]

Attachment: 2014-09-26-10-40-21.png

Steps to reproduce:

1. Call the flame device to activate "missed call" actionable notification on lockscreen. 

2. Open missed call notification from lockscreen. 

3. It takes you to a blank blue screen.

Comment 1

[John Lu [:mnjul][Please NI or I'll miss]]

Greg, could you take a look at this? Thanks.

Comment 2

[Tim Guan-tin Chien [:timdream] (please needinfo)]

This is a dialer app bug.

Comment 3

[Anthony Ricaud (:rik)]

I can't reproduce this on a Flame. It correctly opens the Dialer on the Call log tab.

What is 2.0-VH ?

Comment 4

[Amy Lee [:amylee] UX]

(In reply to Anthony Ricaud (:rik) from comment #3)
> I can't reproduce this on a Flame. It correctly opens the Dialer on the Call
> log tab.
> 
> What is 2.0-VH ?

Hi Anthony, 

I just flashed my device to the latest (Oct 1) engineer master build. It seems now that missed calls don't even appear on lockscreen.

I would ask Tim about the "2.0-VH".

Comment 5

[Johan Lorenzo [:jlorenzo]]

(In reply to Anthony Ricaud (:rik) from comment #3) 
> What is 2.0-VH ?
If you mean "2.0-VH" in "[2.0-VH-bug-bash]", it was a bug bash performed only for the Vertical Homescreen on 2.0. We did that at the time to secure this core 2.0 functionality.

Comment 6

[Anthony Ricaud (:rik)]

Amy: I doubt that we have this error because it is tested by our daily smoketests. So it seems to be on your device only. Have you updated both Gaia and Gecko ?

Comment 7

[Amy Lee [:amylee] UX]

(In reply to Anthony Ricaud (:rik) from comment #6)
> Amy: I doubt that we have this error because it is tested by our daily
> smoketests. So it seems to be on your device only. Have you updated both
> Gaia and Gecko ?

I've updated gaia/gecko and also flashed my phone to the newest base image. I've tested it out on other flame devices and don't have this issue. For whatever reason it only happens on my flame device. But if this isn't a wide issue than this bug can be closed. Thanks!

Comment 8

[Anthony Ricaud (:rik)]

Let's close it then. If it reproduces on more devices, we can always reopen.