Closed
Bug 1239546
Opened 9 years ago
Closed 9 years ago
Sync error No keyFetchToken after OTA
Categories
(Firefox OS Graveyard :: Sync, defect, P1)
Firefox OS Graveyard
Sync
Tracking
(Not tracked)
RESOLVED
FIXED
2.6 S6 - 1/29
People
(Reporter: ariestiyansyah.rizky, Assigned: ferjm)
References
Details
(Keywords: foxfood, Whiteboard: [bzlite])
Attachments
(6 files)
User-Agent: Mozilla/5.0 (Mobile; rv:46.0) Gecko/46.0 Firefox/46.0
1. Go to Settings
2. Select Firefox Sync
3. Press Get started
it will show this account is empty and I try to press sync now then get started again still doesnt work.
In this case my accont already had Firefox Sync in my OSX
Note: Build 20151230201227 dogwood
Reporter | ||
Comment 1•9 years ago
|
||
Reporter | ||
Comment 2•9 years ago
|
||
Reporter | ||
Comment 3•9 years ago
|
||
Reporter | ||
Comment 4•9 years ago
|
||
Reporter | ||
Comment 5•9 years ago
|
||
Comment 6•9 years ago
|
||
Hi Rizky,
Thank you for reporting this.
Please let me ask you a few questions so we can understand and investigate the problem:
-Which device are you using and what is the version (in Settings->Device info->More info)
-Can you tap on that Get started, add your account and then it goes back to that screen (Please see bug 1237731) or it is like you cannot tap on it to introduce your email/pssw?
I have tried with aries latest ota available (20151230) and seems to be working ok.
Thank you!
Flags: needinfo?(ariestiyansyah.rizky)
Reporter | ||
Comment 7•9 years ago
|
||
When tap on get started button isnt working.
My phone: Sony z3c foxfooding device
Flags: needinfo?(ariestiyansyah.rizky)
Comment 8•9 years ago
|
||
Changing to Sync component and ni ferjm to check if he is aware of similar issues. Thanks!
Component: Gaia::Feedback → Sync
Flags: needinfo?(ferjmoreno)
Comment 9•9 years ago
|
||
Just reproduce this. I tapped on Get started and it did not do anything. I had disabled wifi and data, once enabled wifi it worked.
Rizky, could that be your case? Thanks!
Flags: needinfo?(ariestiyansyah.rizky)
Assignee | ||
Comment 10•9 years ago
|
||
Thanks for the report Rizky. I am sorry to say that Firefox Sync is pretty much broken on the latest Sony z3c OTA. This OTA contains an almost one month old code that does not include many of the recent fixes that are already in master.
I can see this error in the logs that you provided: "Sync error No keyFetchToken". This can probably be fixed by login out of your Firefox Accounts and login back in again. But after that you will likely hit bug 1224203 which was not included in the z3c OTA. I am afraid that you'll need to wait for the next OTA update :\
Flags: needinfo?(ferjmoreno)
Summary: Firefox Sync does not work → Sync error No keyFetchToken after OTA
Assignee | ||
Updated•9 years ago
|
Assignee: nobody → ferjmoreno
Blocks: fxos-sync
Priority: -- → P1
Target Milestone: --- → 2.6 S6 - 1/29
Comment 11•9 years ago
|
||
Assignee | ||
Comment 12•9 years ago
|
||
Comment on attachment 8711138 [details] [review]
[gaia] ferjm:bug1239546.nokeyfetchtoken.patch > mozilla-b2g:master
It is possible that devices getting an OTA where the user is already logged into FxA and where the fix from bug 1211606 is not present or was never executed (i.e. the user didn't logout/login from FxA) hit the "No key fetch token" error. In this case, the only thing that we can do is to log the user out of her FxA and ask her to login again.
As usual, Michiel, could you review the Sync part, please? Yura, could look at the Settings one, please? Thanks!
Attachment #8711138 -
Flags: review?(yzenevich)
Attachment #8711138 -
Flags: review?(mbdejong)
Updated•9 years ago
|
Attachment #8711138 -
Flags: review?(mbdejong) → review+
Comment 13•9 years ago
|
||
Comment on attachment 8711138 [details] [review]
[gaia] ferjm:bug1239546.nokeyfetchtoken.patch > mozilla-b2g:master
Looks good with 1 problem addressed. Thanks
Attachment #8711138 -
Flags: review?(yzenevich) → review+
Reporter | ||
Comment 14•9 years ago
|
||
It solve my problem by login out and log in again. awesome
Flags: needinfo?(ariestiyansyah.rizky)
Assignee | ||
Comment 15•9 years ago
|
||
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Comment 16•9 years ago
|
||
To allow TVs to OTA from 2.1 to 2.5 later this year, this will need to be fixed in tv_apps/smart-system, and then be uplifted to 2.5, right?
Flags: needinfo?(ferjmoreno)
Assignee | ||
Updated•9 years ago
|
blocking-b2g: --- → 2.5?
Flags: needinfo?(ferjmoreno)
Assignee | ||
Comment 17•9 years ago
|
||
Maybe not. Is the 2.1 TV shipping with FxA integration?
blocking-b2g: 2.5? → ---
Flags: needinfo?(yliao)
Flags: needinfo?(jocheng)
Comment 18•9 years ago
|
||
(In reply to Fernando Jiménez Moreno [:ferjm] from comment #17)
> Maybe not. Is the 2.1 TV shipping with FxA integration?
Hi Fernando,
We will not support FxA integration in 2.1. OTA should not be an issue for TV.
Flags: needinfo?(jocheng)
Updated•9 years ago
|
Flags: needinfo?(yliao)
You need to log in
before you can comment on or make changes to this bug.
Description
•