Closed
Bug 908124
Opened 12 years ago
Closed 12 years ago
An error message is shown after successfully open a received photo and click 'home' key.
Categories
(Firefox OS Graveyard :: Gaia::Bluetooth, defect)
Tracking
(blocking-b2g:leo+, b2g18 fixed, b2g-v1.1hd fixed)
RESOLVED
FIXED
blocking-b2g | leo+ |
People
(Reporter: echou, Assigned: iliu)
References
Details
Attachments
(1 file)
Assignee | ||
Updated•12 years ago
|
Assignee: nobody → iliu
I'm not able to reproduce the issue on mozilla-central-inari-eng. Test environment is as following:
Build: Gaia::master / Gecko::mozilla-central, id: 20130825040201
Device: inari
I will do it again on Gaia::v1-train / Gecko::b2g18.
Assignee | ||
Comment 2•12 years ago
|
||
I'm able to reproduce the issue on Gaia::v1-train / Gecko::b2g18 . And no need to share a photo from Facebook app.
The root cause is received 'ActivityCanceled' event which is fired via Gecko and handled in activity.onerror scope. Then, Bluetooth file transfer don't identify the error case. And pop out the error dialog with unknown media message.
Since Bug 838898 is fixed in Gaia:master, so that we're able to reproduce it on Gaia::v1-train only. But the fixing patch is handling the 'NO_PROVIDER' only. I would like to give a patch to handle it and 'ActivityCanceled' clearly. The 'ActivityCanceled' event will be triggered while requesting an activity and a user click 'home' key.
Nominating leo+..
blocking-b2g: --- → leo?
Assignee | ||
Updated•12 years ago
|
Summary: An error message is shown after successfully open a received photo → An error message is shown after successfully open a received photo and click 'home' key.
Assignee | ||
Comment 3•12 years ago
|
||
Alive,
Could you please help to review my pr? Thanks.
Attachment #795327 -
Flags: review?(alive)
Comment 4•12 years ago
|
||
Comment on attachment 795327 [details]
Pointer to Github pull request 11752.html
r=me
Attachment #795327 -
Flags: review?(alive) → review+
Assignee | ||
Comment 5•12 years ago
|
||
Thanks for Alive's reviewing effort.
Gaia/master:: c229460290fb34f6e7d050b354e5ffb09a4f9cdb
Wait the nominating process for landing on v1-train. Then, we can close the issue.
Comment 7•12 years ago
|
||
We discussed in triage that it may be a recent regression, patch is very straight forward, hence leo+
blocking-b2g: leo? → leo+
Assignee | ||
Comment 8•12 years ago
|
||
Gaia/v1-train:: 577ab5105af418efc8ded00798fd3644b3dac674
Shell we uplift to v1.1.0hd? Nominating hd+, since the patched landed on v1-train.
Comment 9•12 years ago
|
||
v1.1.0hd: 577ab5105af418efc8ded00798fd3644b3dac674
Assignee | ||
Comment 11•12 years ago
|
||
I think we don't need other patch for this bug. Since the patch is landed on v1.1.0hd, we can close the issue now. Thanks for Tim's reminder and uplifting process.:)
Status: NEW → RESOLVED
Closed: 12 years ago
Flags: needinfo?(iliu)
Resolution: --- → FIXED
Comment 12•12 years ago
|
||
This was leo+, leo+ already covers hd+.
Setting back to leo+.
blocking-b2g: hd? → leo+
You need to log in
before you can comment on or make changes to this bug.
Comment 1
•