All pre-filled IMAP options should include the disclaimer "Do not try to use your account password. It will not work. You must use an app password."
#160
AppPasswordSetupScreen.kt is the shared guided-setup screen for every preset provider with
pre-filled IMAP/SMTP servers (Gmail, Yahoo, iCloud today; AOL pending #154/#156). It already shows
an InfoCard warning (app_password_warning = "Store this app password carefully — it grants
full access to your email. LibreMail keeps it only on this device.") but never explicitly says
that the user's regular account password will not work in the "App password" field
(app_password_field). New users unfamiliar with the app-password concept commonly try their
normal password first and get a confusing auth failure instead of a clear steer.
Scope
Add the disclaimer "Do not try to use your account password. It will not work. You must use
an app password." as a new string resource, shown on AppPasswordSetupScreen.kt — most
usefully right next to the "App password" field (app_password_field, ~line 183-191) where
the user is about to type, rather than only in the intro InfoCards above.
Since this screen is shared by every preset provider (providerIntro()), one change covers
Gmail/Yahoo/iCloud today and AOL once #154/#156 land — no per-provider copy needed.
ManualSetupScreen.kt is explicitly out of scope: its servers aren't pre-filled, its
password field is already labeled "Password or app password", and some manually configured
IMAP servers genuinely do use the account password — the blanket disclaimer wouldn't be
universally true there.
Acceptance criteria
Every guided (pre-filled-server) provider setup screen shows the disclaimer near the app-password
field.
## Context
`AppPasswordSetupScreen.kt` is the shared guided-setup screen for every preset provider with
pre-filled IMAP/SMTP servers (Gmail, Yahoo, iCloud today; AOL pending #154/#156). It already shows
an `InfoCard` warning (`app_password_warning` = "Store this app password carefully — it grants
full access to your email. LibreMail keeps it only on this device.") but never explicitly says
that the user's *regular account password* will not work in the "App password" field
(`app_password_field`). New users unfamiliar with the app-password concept commonly try their
normal password first and get a confusing auth failure instead of a clear steer.
## Scope
- [ ] Add the disclaimer "Do not try to use your account password. It will not work. You must use
an app password." as a new string resource, shown on `AppPasswordSetupScreen.kt` — most
usefully right next to the "App password" field (`app_password_field`, ~line 183-191) where
the user is about to type, rather than only in the intro `InfoCard`s above.
- [ ] Since this screen is shared by every preset provider (`providerIntro()`), one change covers
Gmail/Yahoo/iCloud today and AOL once #154/#156 land — no per-provider copy needed.
- [ ] `ManualSetupScreen.kt` is explicitly out of scope: its servers aren't pre-filled, its
password field is already labeled "Password or app password", and some manually configured
IMAP servers genuinely do use the account password — the blanket disclaimer wouldn't be
universally true there.
## Acceptance criteria
- Every guided (pre-filled-server) provider setup screen shows the disclaimer near the app-password
field.
- Manual IMAP/SMTP setup is unchanged.
## Relevant files
- `ui/accountsetup/AppPasswordSetupScreen.kt`, `res/values/strings.xml`
(`app_password_*` block).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Context
AppPasswordSetupScreen.ktis the shared guided-setup screen for every preset provider withpre-filled IMAP/SMTP servers (Gmail, Yahoo, iCloud today; AOL pending #154/#156). It already shows
an
InfoCardwarning (app_password_warning= "Store this app password carefully — it grantsfull access to your email. LibreMail keeps it only on this device.") but never explicitly says
that the user's regular account password will not work in the "App password" field
(
app_password_field). New users unfamiliar with the app-password concept commonly try theirnormal password first and get a confusing auth failure instead of a clear steer.
Scope
an app password." as a new string resource, shown on
AppPasswordSetupScreen.kt— mostusefully right next to the "App password" field (
app_password_field, ~line 183-191) wherethe user is about to type, rather than only in the intro
InfoCards above.providerIntro()), one change coversGmail/Yahoo/iCloud today and AOL once #154/#156 land — no per-provider copy needed.
ManualSetupScreen.ktis explicitly out of scope: its servers aren't pre-filled, itspassword field is already labeled "Password or app password", and some manually configured
IMAP servers genuinely do use the account password — the blanket disclaimer wouldn't be
universally true there.
Acceptance criteria
field.
Relevant files
ui/accountsetup/AppPasswordSetupScreen.kt,res/values/strings.xml(
app_password_*block).