Firefox-ios: FXIOS-366 ⁃ notDecrypted receiving a tab
All 16 comments
Any theories as to why? Or if there is something we can do to recover from that state? I assume it is persistently bad for you and not an intermittent thing
garvankeeley
on 27 Apr 2020
Was the Beta upgraded from prev such that you were already signed-in to sync? Or could this be a migration problem. This debug error is new, in the past it would just say "Tap to begin", and we had regular reports of that error in the past. Any guess as whether this is a new issue or might it be the old "Tap to begin" bug resurfaced as this error?
garvankeeley
on 27 Apr 2020
Any theories as to why? Or if there is something we can do to recover from that state? I assume it is persistently bad for you and not an intermittent thing
Not sure, maybe we should log more information, because it could be related to a lot of things currently.
eoger
on 27 Apr 2020
Do you have more than one build installed? Both beta and release?
I just had this error, but after uninstalling all other versions on my device and restarting the Beta I can't repro that error anymore. I am wondering if handling the sendtab message by multiple copies of the app is possible.
garvankeeley
on 27 Apr 2020
Only one build (no Firefox release installed), and I can reproduce reliably.
eoger
on 27 Apr 2020
A new v25 beta will be out within the hour. It will be interesting to see if that fixes it.
garvankeeley
on 27 Apr 2020
Was able to successfully receive a tab iPhone 11 with beta 17793 and OS 13.3.1. Sending from Nightly 77.0a1
athomasmoz
on 28 Apr 2020
Same but seems intermittent, sometimes no tab is received. However, an intermittent response would not relate to this bug.
garvankeeley
on 28 Apr 2020
Closing as this seems to be a false alarm, I can't repro, but I was definitely in a state where the logins and passwords screen was empty.
Did you mean to close another bug?
eoger
on 28 Apr 2020
Sorry yeah
garvankeeley
on 28 Apr 2020
Removing release blocker tag as we only have this report so far on Beta. It is being heavily tested by QA and so far it is looking ok.
garvankeeley
on 28 Apr 2020
The error has now changed to showing this error https://searchfox.org/mozilla-mobile/source/application-services/components/fxa-client/src/device.rs#148
The code may be hitting this, needs more logging to know for sure: https://searchfox.org/mozilla-mobile/rev/5ddcdb1fc493e29cce76a5e57ae12a02dc6305be/application-services/components/fxa-client/src/device.rs#182-185
Re-opening this bug unless we open another one to track the changed error.
garvankeeley
on 1 May 2020
Opened a PR that might fix the problem: https://github.com/mozilla/application-services/pull/3065
eoger
on 1 May 2020
Confirming that testing the a-s patch above fixes the error seen on iOS. The patch catches the decryption error and resets the necessary keys.
garvankeeley
on 4 May 2020
Update: we're still seeing issues such as "Could not find refresh token" (it should ALWAYS be present).
I found some errors Access to item attempted while keychain is locked in the console.
eoger
on 5 May 2020
Update: https://github.com/mozilla/application-services/issues/3083 seems to be the culprit here.
eoger
on 6 May 2020
Related issues
sleroux
·
4Comments
shree007
·
5Comments
Scripter17
·
8Comments
kundan52
·
3Comments
farhanpatel
·
8Comments