Skip to content

[$500] iOS - Settings - The keyboard appears with a black background that changes to grey #37301

Closed

Description

@kbecciv

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


Version Number: 1.4.44.0
Reproducible in staging?: y
Reproducible in production?: n
Issue reported by: Applause - Internal Team
Issue found when executing PR: #35326

Action Performed:

  1. Go to personal details
  2. Tap on address
  3. Tap on country
  4. Navigate back
  5. Tap on country again

Expected Result:

It should only show a grey background.

Actual Result:

The keyboard appears with a black background that changes to grey.

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

Bug6393976_1709037272812.VYHS1315.1.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~0196694799b239c5ad
  • Upwork Job ID: 1762484844314882048
  • Last Price Increase: 2024-02-27

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    ExternalAdded to denote the issue can be worked on by a contributor
    on Feb 27, 2024
  2. melvin-bot commented on Feb 27, 2024

    @melvin-bot
  3. changed the title [-]iOS - Settings - The keyboard appears with a black background that changes to grey[/-] [+][$500] iOS - Settings - The keyboard appears with a black background that changes to grey[/+] on Feb 27, 2024
  4. added
    Help WantedApply this label when an issue is open to proposals by contributors
    on Feb 27, 2024
  5. melvin-bot commented on Feb 27, 2024

    @melvin-bot

    Triggered auto assignment to Contributor-plus team member for initial proposal review - @mkhutornyi (External)

  6. github-actions commented on Feb 27, 2024

    @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.
  7. melvin-bot commented on Feb 27, 2024

    @melvin-bot

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

  8. ikevin127 commented on Feb 27, 2024

    @ikevin127
    Contributor

    Proposal

    Please re-state the problem that we are trying to solve in this issue

    I was not able to find any offending PR within the deploy checklist, so I'm assuming this was not caused by the latest deploy.

    What is the root cause of that problem?

    We're not leveraging the iOS specific keyboardAppearance TextInput prop and because of this, the 'default' applies which will default to the appearance that the user has set globally on their device, which typically is a light keyboard but will be dark if the user has chosen to use the system-wide dark mode in their iOS settings.

    This can cause the unwanted transition from dark to light if not specifically set.

    What changes do you think we should make in order to solve the problem?

    Since the Expected result states:

    It should only show a grey background.

    this means we always want to show the light keyboard background.

    For this we should explicitly set keyboardAppearance to light here.

    Videos

    iOS: Native
    Before After
    before.mov
    after.mov
  9. mkhutornyi commented on Feb 27, 2024

    @mkhutornyi
    Contributor

    I think #29991 is the offending PR.
    So retest after #37305 is deployed to staging

  10. puneetlath commented on Feb 27, 2024

    @puneetlath
    Contributor

    Can confirm it's working fine now after the revert. Closing this issue, but feel free to reopen if there's still something that needs to be done.

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

Metadata

Metadata

Labels

EngineeringExternalAdded to denote the issue can be worked on by a contributorHelp WantedApply this label when an issue is open to proposals by contributorsHourlyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions