thunderbird / thunderbird/thunderbird-android
OAuth 2 fails for IMAP on Android with Outlook
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 14k
- Forks
- 2.8k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 57
Description
Checklist
- I have used the search function to see if someone else has already submitted the same bug report.
- I will describe the problem with as much detail as possible.
App version
6.802
Where did you get the app from?
Google Play
Android version
14
Device model
Galaxy S23 Ultra SM-S918W
Steps to reproduce
Sorry, the steps to reproduce is MS Outlook (or something) asking the K-9 app to re-authenticate. Or at least I think that is the problem.
K-9 just then gives the spinning circle forever. Restarting just gives the spinning circle forever. My mailer on other computers continue to accept mail without problem.
I'm using K-9 on a Samsung Galaxy S23 Ultra and my email incoming server is outlook.office365.com, outgoing is smtp.office365.com, both using authentication method OAuth2. I'm using my work account.
I used to be able to solve this problem (2022 or so?) by going to Settings --> myaccount --> Fetching Mail --> Incoming Server and just clicking on Next. This used to bring up my work account login, followed by the MS Authenticator. Now it just deletes my account credentials, so far as I can tell, and lands me on "Welcome to Outlook" -- all inbox, sent, etc folders empty. The solution so far is to delete my account and then build it again.
Expected behavior
I would expect that when OAuth2 reauthentication is requested, that K-9 would open the reauthentication dialog boxes and then communicate accordingly with MS Authenticator.
Actual behavior
Just hangs with a spinning circle. I've no idea what K-9 is actually doing.
I want to also note that I tried to report this issue by signing up to the K-9 Mail Forum. But it would never send me a confirmation email, despite my asking it to resend 3 times and my repeatedly checking my junk folder. Something wrong there?
Logs
Sorry, there are no logs. K-9 didn't think it had a problem.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing OAuth2 reauthentication from Settings → the account → Fetching Mail → Incoming Server on Android 14 with an Outlook work account. There are no logs or named files and the trigger is uncertain; done means reauthentication opens the expected login and Authenticator flow instead of hanging or losing credentials.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- authentication, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100