Mobile app won't scan QR code for import if an account was set to no-authentication
Categories
(Thunderbird :: General, defect)
Tracking
(Not tracked)
People
(Reporter: pda, Unassigned)
References
Details
Attachments
(1 file)
148.05 KB,
image/png
|
Details |
Steps to reproduce:
Followed steps at https://support.mozilla.org/en-US/kb/thunderbird-android-import
Desktop is Debian Linux, mobile is Android 14 on a Samsung.
Actual results:
Nothing... what else to say?
Expected results:
Not sure, I've never had this succeed.
Comment 1•11 months ago
|
||
https://support.mozilla.org/en-US/kb/thunderbird-android-import states minimum requirements.
What version of Thunderbird are you using?
What version of mobile Thunderbird, where installed from?
The QR code is generated, and what happens on the Android?
To be more precise than above, desktop is 128.5.0esr.
Mobile is latest version from Google play; there's no apparent way to see any number without setting up app first.
Camera gets opened to do a scan, but nothing else afterwards, i.e. no scan, but no error or anything.
Comment 3•11 months ago
|
||
Are you trying to export multiple accounts or just one account? Have you tried without exporting passwords? If you click through on desktop, is the summary accurate for what you selected?
I'm exporting 8 accounts, which is why I'm trying hard to get this working.
Thanks for the passwords suggestion, unchecking this option does give some progress, but not complete success.
The desktop generates 3 QR codes, and I see now that I can hit the "Next" button to read the second and third ones.
Still no dice for the first of the 3 QR codes, so not all accounts are recognized.
Comment 5•11 months ago
|
||
(In reply to Paul from comment #4)
Thanks for the passwords suggestion, unchecking this option does give some progress, but not complete success.
Okay, so with the passwords option checked it doesn't even advance to the QR codes? It might be trying to prompt you to allow exporting the passwords, as it would when you show the passwords in the password manager (except on Linux where this check is not performed).
The desktop generates 3 QR codes, and I see now that I can hit the "Next" button to read the second and third ones.
Still no dice for the first of the 3 QR codes, so not all accounts are recognized.
Note that one QR code can contain more than one account, the summary at the end shows what was contained in the QR codes, and the Android app should also show you all accounts if it successfully scans all (three) codes.
If the Android app is refusing to scan at least one of the codes, can you try only exporting some of the accounts, so we can maybe reduce this to one or more specific accounts? That should make it easier to find properties of the accounts that might be the issue.
I assume you've found out that you can always restart the QR code import in the app to import new accounts in the Android app from the settings. So only exporting some of the accounts should not be an issue.
Thanks for suggestions... the problem doesn't see to be with the particular accounts.
I'm not certain I can repeat this behaviour every time, but my observation is:
- The 2 accounts that fail in my original scenario can export fine by themselves.
- Doing the other 6 without the 2 presumably problematic ones does not work either, only the second of two QR codes is read in this case.
So it would seem the issue is with the first QR code when there are multiples.
Does that help?
While there may be a problem importing more than 3 accounts, that may not be all.
I thought I could import my accounts in groups of 2 or 3 at a time, I did end up having trouble reading the QR code for a particular one.
What details about this are worth adding to this bug report?
Comment 8•10 months ago
|
||
We'd have to see what data was produced for https://searchfox.org/comm-central/rev/7587b30e4939f291bb0f4dd1a9abec0f8e38f780/mail/modules/QRExport.sys.mjs#125 (would be good to log that.)
Are you able to provide a screenshot of the problematic qr code? (Without the password).
This is the QR for the one particular email account I'm unable to import into Android Thunderbird.
Comment 10•10 months ago
|
||
Thanks, what is the authentication method of that account? It's being mapped to null
Reporter | ||
Comment 11•10 months ago
|
||
That's strange, it's blank in my desktop account setting too. Thunderbird is still reading its mail, however.
I suppose I should set this, then see if my Android import problem goes away?
Comment 12•10 months ago
|
||
Probably, but before you do that, please check what the value is.
If you go to settings and go to the config editor, can you check what value authMethod
has for that account.
I assume this profile may be very very old, over 15yrs old?
Reporter | ||
Comment 13•10 months ago
|
||
I think I found the config editor you mention, but I can't tell which of the multiple (numbered) servers is the one to look at.
There's only one that has a zero for authMethod, so I'd guess that's the one.
I only actually re-started using thunderbird again after a long time. It's remotely possible started from an old profile left in my home directory after several years; I can't tell at this point, but it seems unlikely.
Comment 14•10 months ago
|
||
You can find out the correlation with Help -> Troubleshooting Information where all the accounts are listed including their ID, which is the number used in the prefs. It might also be able to show the actual authentication method there, without needing to look at the raw pref value.
Reporter | ||
Comment 15•10 months ago
|
||
str |
Sorry, forgot this for a few days... After changing the account from no-authentication to "Normal password", I am then able to export all the accounts to a couple of new devices. Choosing whether or not to export passwords makes no difference either.
Comment 16•10 months ago
|
||
I had the same problem. I have 10 acounts and only one account couldn't be imported (QR-code couldn't be read). After comparing this account with another one (which worked) I saw that the problematic accoutn had an additional alias mail (identity). After removing this alias, the account could be imported. Hope this helps...
Updated•9 months ago
|
Comment 18•8 months ago
|
||
This bug was the cause of my problem.
I generated a QR code from desktop app version 128.
I tried to scan the QR code to import settings into the thunderbird android app version 8.2
it would not register the QR code, it just stayed stuck in camera mode.
I scanned the QR code with another QR code app and found that one of my email accounts had a 'null' value for it's authentication.
In my cause it was an imap account for incoming mail, which i also paired with an smtp account using oauth2 authentication for outgoing mail.
So, in the thunderbird desktop app I changed the imap account's authentication type to Oauth2 -- oddly enough once I did this I no longer had the option to set it blank again.
After that I generated a new QR code and the android app picked it up just fine.
Comment 19•8 months ago
|
||
This bug is likely resolved with the patch from bug 1930728 - in the sense that it will filter such accounts.
Roland, do you think we need to update user documentation to point out that "empty" fields in the server authentication method will also make the account unavailable for export but switching to an available option will make it available?
Comment 20•8 months ago
|
||
If there are indeed "empty" fields, that seems like a bug that should be fixed.
Now after bug 1930728 , you can set mail.qrexport.loglevel
to All
to figure out why something wouldn't export. It will log it to the Error Console (Ctrl+Shift+J)
Comment 21•8 months ago
•
|
||
(In reply to Martin Giger [:freaktechnik] from comment #19)
This bug is likely resolved with the patch from bug 1930728 - in the sense that it will filter such accounts.
Roland, do you think we need to update user documentation to point out that "empty" fields in the server authentication method will also make the account unavailable for export but switching to an available option will make it available?
is this SMTP settings or receiving settings or both Martin? And how does a user set the authentication method to empty
?
Comment 22•8 months ago
|
||
(In reply to Roland Tanglao from comment #21)
is this SMTP settings or receiving settings or both Martin? And how does a user set the authentication method to
empty
?
This would affect both. After testing by manually setting the auth methods of an account I'm fairly certain bug 1930728 doesn't fix this yet. So how you'd end up with an empty field is yet to be determined. I guess bug 1930728 still changed the allowed auth methods, but the ones Magnus excluded have actual labels when active.
Though it seems any value we don't support (like 0 or 11) leads to the empty field. I wonder if for some accounts the default value isn't being set/read correctly or similar.
Anyone encountering this: still interested to hear about your prefs, or the new logging Magnus mentioned in comment #20.
Comment 23•6 months ago
|
||
Paul, do you still see this?
If still a problem, to to Settings | Config editor (about:config). Then change mail.qrexport.loglevel
to All
. Try to export and report what you get in the Error Console (Ctrl+Shift+J)
Reporter | ||
Comment 24•6 months ago
|
||
I did the workaround on this months ago, so I would need to go back to my original scenario on a new install to test.
Is it worth the trouble?
Maye so, as the above comments make It sound a bit ambiguous as to whether this might've been fixed.
Description
•