OAuth authentication error display does not work in release builds

Open
#11,916 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 3 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
android, kotlin

Research direction

Compare OAuth2 authentication failure handling in debug and release builds, starting with the Android app's authentication and error display entry points. Reproduce the expired-token flow after revoking provider access, then trace why release builds leave mail loading and sending without a user-facing error; done when both operations report the failure in a release build.

Written by the indexing model from the issue text.

Description

unconfirmed
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

Thunderbird for Android

App version

24.0

Where did you get the app from?

Google Play

Android version

15

Device model

Fairphone 5

Steps to reproduce
  1. Login to a mail provider with OAuth2, like google
  2. All mails appear
  3. End session via Identity provider (Google)
  4. Wait a few minutes, until the access token of the app expires
  5. Reload the mails, the loading spinner spins for a long time, no error message appears
Expected behavior

Try the same in a debug build (like cloning the repo, building and running it directly on the phone does produce this error message:

Screenshot_20261111-204810
Actual behavior

Just a loading spinner, forever. No user facing error message, no new mails. Mail sending does not work as well, mails stay in Outgoing, again without any error message.

Logs

No response

Dominant language
Kotlin
Stars
14.2k
Forks
2.9k
Avg merge
3d 8h
Merged PRs (30d)
79

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from thunderbird/thunderbird-android

All issues in thunderbird/thunderbird-android

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.