Closed
Bug 1028726
Opened 10 years ago
Closed 10 years ago
[Flame][v1.3] The list of missed call numbers doesn't save in call log
Categories
(Firefox OS Graveyard :: Gaia::Dialer, defect)
Firefox OS Graveyard
Gaia::Dialer
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: suncha629, Unassigned)
References
Details
(Keywords: b2g-testdriver)
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:33.0) Gecko/20100101 Firefox/33.0 (Beta/Release) Build ID: 20140613030203 Steps to reproduce: Get missed call Actual results: When somebody gives me missed call, it doesn't show in "Call Log" and disappears from the device totally. Though the notification bar gives me a missed call alert, but when I press it then nothing happen and disappear. Expected results: The list of missed call numbers should record in the Call log.
Keywords: b2g-testdriver
Whiteboard: The list of missed call numbers doesn't save in call log
Summary: Flame → The list of missed call numbers doesn't save in call log in Flame
Component: General → Gaia::Dialer
Summary: The list of missed call numbers doesn't save in call log in Flame → [Flame][v1.3] The list of missed call numbers doesn't save in call log
Comment 3•10 years ago
|
||
This scenario is tested daily so I'm surprised you're seeing this. Are you still seeing this?
Flags: needinfo?(suncha629)
Whiteboard: The list of missed call numbers doesn't save in call log
Bro, I am extremey Sorry for late replay, It's been fixed long time ago, but my account had been hacked and after a long hard work, have recovered the account. Thank you...(In reply to Anthony Ricaud (:rik) from comment #3) > This scenario is tested daily so I'm surprised you're seeing this. Are you > still seeing this?
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Flags: needinfo?(suncha629)
Resolution: --- → WORKSFORME
Comment 5•10 years ago
|
||
Hi, I probably do not exactly get "where" is the issue "fixed" and "tested daily", but I am definitely having this exact same issue on my Flame with FxOS v1.3. In flashed nightly v2.1, the issue does not occur, but after flashing back to the official base image with v1.3 the issue is back again (have not tried other versions). So I have to confirm, that the issue is very real in the v1.3 the Flames are shipped with, and also in the official base image (which is the same build I guess). There are also others reporting this: http://blog.angeloff.name/post/2014/09/01/day2-7-using-firefox-os/ Best regards, Jan Jansky
You need to log in
before you can comment on or make changes to this bug.
Description
•