Closed
Bug 1250351
Opened 10 years ago
Closed 8 years ago
Authorization code failures during Updates are listed as "transfer error: Failed (unknown reason), default code: 2152398849" in the logcat
Categories
(Firefox OS Graveyard :: Gaia::System, defect)
Tracking
(b2g-master affected)
RESOLVED
WONTFIX
| Tracking | Status | |
|---|---|---|
| b2g-master | --- | affected |
People
(Reporter: Marty, Unassigned)
Details
(Whiteboard: [2.6-Daily-Testing][Spark])
Attachments
(1 file)
|
13.77 KB,
text/plain
|
Details |
Description:
When the user attempts to perform a system update, but there is an authorization code failure, the logcat shows it as:
"02-22 13:46:55.684: I/GeckoConsole(323): AUS:SVC getStatusTextFromCode - transfer error: Failed (unknown reason), default code: 2152398849"
This error message is not understandable to see what went wrong.
Authentication is currently failing for Whitelisted devices (Bug 1250330)
Repro Steps:
1) Update a Whitelisted Aries to 20151023103433
2) Attempt to install an update on the dogfood or dogfood-test channels
3) After the update fails, examine the logcat
Actual:
The error message for the failed download is listed as "unknown reason"
Expected:
The error message for the failed download is understandable, and indicates the reason for failure.
Environmental Variables:
Device: Aries 2.5
Build ID: 20151023103433
Gaia: 410e91ddabc7ba82a9b43b3711a3fdf2cb8de309
Gecko: 13f32d98ff20718496bd08eb610950429a343f42
Gonk: 2916e2368074b5383c80bf5a0fba3fc83ba310bd
Version: 44.0a1 (2.5)
Firmware Version: D5803_23.1.A.1.28_NCB.ftf
User Agent: Mozilla/5.0 (Mobile; rv:44.0) Gecko/44.0 Firefox/44.0
Repro frequency: 10/10
See attached: logcat
| Reporter | ||
Updated•10 years ago
|
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Updated•10 years ago
|
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker) → needinfo?(nhirata.bugzilla)
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(nhirata.bugzilla)
Resolution: --- → DUPLICATE
Ack sorry. I forgot the reason why this bug existed. This bug exists because the log isn't clear. I guess I need to slow down a little. The other bug is in regards to the root issue.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Comment 3•8 years ago
|
||
Firefox OS is not being worked on
Status: REOPENED → RESOLVED
Closed: 10 years ago → 8 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•