Skip to content

[Due for payment 2026-09-16] Android - Login - Terms of Service and Privacy link are not underlined in high contrast mode #97409

Description

@applause-bot

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.


Version Number: 9.4.46-0
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #96618
Email or phone of affected tester (no customers): sdsjodijnsdojsosjio@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Samsung Galaxy S25 FE / Android 16
App Component: Other

Action Performed:

Precondition:

  • Device is Android 16.
  • Device font size is minimum.
  1. Launch Expensify app.
  2. Log out if logged in.
  3. Click Enable high contrast.
  4. Enter new email > Next.

Expected Result:

Terms of Service and Privacy link will be underlined in high contrast mode.

Actual Result:

Terms of Service and Privacy link are not underlined in high contrast mode.

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome Safari

Screenshots/Videos

Bug7221285_1785360047041.Screen_Recording_20260730_051955_Expensify.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Mita Rachim
Bug ID: 7221285

Issue OwnerCurrent Issue Owner: @mallenexpensify

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Jul 29, 2026
  2. applause-bot commented on Jul 29, 2026

    @applause-bot
    Author

    While Applause doesn't embed attachments for this bug, here are the links for quick view:
    https://platform.applause.com/services/links/v1/external/974a0807ae251d3e37af6765f345640b7d022e020532e6e8a99a75f76444e808

  3. melvin-bot commented on Jul 29, 2026

    @melvin-bot

    @jasperhuangg recently merged #96618, but they are OOO right now, so I'll auto-assign someone else.

  4. melvin-bot commented on Jul 29, 2026

    @melvin-bot

    Triggered auto assignment to @rlinoz (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  5. melvin-bot commented on Jul 29, 2026

    @melvin-bot

    @jasperhuangg @Pujan92 @rushatgabhane you have been assigned to this deploy blocker because you reviewed the offending PR: #96618

  6. melvin-bot commented on Jul 29, 2026

    @melvin-bot

    💬 A slack conversation has been started in #expensify-open-source

  7. github-actions commented on Jul 29, 2026

    @github-actions
    Contributor

    👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

    1. Identify the pull request that introduced this issue and revert it.
    2. Find someone who can quickly fix the issue.
    3. Fix the issue yourself.
  8. 53 remaining items

  9. melvin-bot commented on Sep 15, 2026

    @melvin-bot

    Payment Summary

    Resolving PRs:

    BugZero Checklist (@mallenexpensify)

    • I have confirmed assignees, roles, and Upwork contracts look correct
    • I have paid out Upwork contracts / manual NewDot requests
    • [BugZero Assignee] I have created a GH issue for creating/updating the regression test once above steps have been agreed upon
  10. melvin-bot commented on Sep 18, 2026

    @melvin-bot

    @mallenexpensify Whoops! This issue is 2 days overdue. Let's get this updated quick!

  11. mallenexpensify commented on Sep 21, 2026

    @mallenexpensify
    Contributor

    @mkhutornyi from the C+ doc

    If a post on the PR or the issue mentions a regression or a deploy blocker, the C+ must post on the issue before the payment date.

    Post one of these two:

    It was a regression. Say so. Pay drops 50% for each regression on the issue.

    It was not a regression. Give the reason, and include all three:

    • Quote the sentence that settles it, as a blockquote. Use a screenshot only when the proof is visual.
    • Link the exact comment, not the issue,
    • State who closed the linked blocker and whether a PR closed it. A blocker the CME closed with no fix PR is not a regression. A blocker closed by a fix PR is one.

    If the C+ does not post by the payment date, the CM assumes every mention of a regression or a deploy blocker reduces the amount.

  12. mkhutornyi commented on Sep 22, 2026

    @mkhutornyi
    Contributor

    @mallenexpensify I am not sure why you posted that message.
    There was no post on the PR or the issue mentioning a regression or a deploy blocker.

    This issue itself is deploy blocker but I didn't review original PR.

  13. mallenexpensify commented on Sep 22, 2026

    @mallenexpensify
    Contributor

    @mkhutornyi Melvin assigned this blocker to the reviewers of the offending PR #96618, and you weren't one of them, so no reduction here. I pay 100+ issues a week. Many carry deploy blocker text or labels. Sometimes the issue is a regression, sometimes the linked PR caused one. I can't read every issue and PR, so I need the C+ on the PR to post the detail. If nobody posts, I apply the reduction.

  14. mallenexpensify commented on Sep 22, 2026

    @mallenexpensify
    Contributor

    Payment Summary

    Contributor+: @mkhutornyi due $250 via NewDot

  15. mallenexpensify commented on Sep 22, 2026

    @mallenexpensify
    Contributor

    @mkhutornyi I posted in #contributor-plus about and updated the C+ process doc to be more clear.

  16. trjExpensify commented on Oct 1, 2026

    @trjExpensify
    Contributor

    approved $250 for @mkhutornyi

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2EngineeringNeeds ReproductionReproducible steps needed

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions