You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Awaiting checklist] [$250] Contact method - Keyboard not opened when navigating to enter magic code step #51279
Version Number: 9.0.52.1 Reproducible in staging?: Y Reproducible in production?: N/A - new feature, doesn't exist in prod If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Y Issue was found when executing this PR:#49445 Issue reported by: Applause Internal Team
Action Performed:
Open the app and log in
Navigate to the account settings > Profile > Contact method
Tap the New contact method button
Enter an email that will be used as a secondary login
👋 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:
Identify the pull request that introduced this issue and revert it.
changed the title [-][$250] Contact method - Keyboard not opened when navigating to enter magic code step[/-][+][HOLD for payment 2024-11-22] [$250] Contact method - Keyboard not opened when navigating to enter magic code step[/+]on Nov 15, 2024
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.62-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@Ollyws@twisterdotcom@Ollyws The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
changed the title [-][HOLD for payment 2024-11-22] [$250] Contact method - Keyboard not opened when navigating to enter magic code step[/-][+][Awaiting checklist] [$250] Contact method - Keyboard not opened when navigating to enter magic code step[/+]on Nov 22, 2024
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion:
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
Regression Test Proposal Template
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue:
Regression Test Proposal
Precondition:
Test:
1. Open settings > Profile > Contact method
2. Tap the New contact method button
3. Enter any email that will be used as a secondary login
4. Press on anywhere to close the keyboard
5. Proceed to the magic code step
6. Verify the magic code input is focused and a keyboard is shown (mobile)
Activity
melvin-bot commentedon Oct 22, 2024
Triggered auto assignment to @cead22 (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Oct 22, 2024
Triggered auto assignment to @twisterdotcom (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.melvin-bot commentedon Oct 22, 2024
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Oct 22, 2024
👋 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:
cead22 commentedon Oct 22, 2024
I couldn't reproduce on iOS native, but regardless, this doesn't need to be a blocker
21 remaining items
[-][$250] Contact method - Keyboard not opened when navigating to enter magic code step[/-][+][HOLD for payment 2024-11-22] [$250] Contact method - Keyboard not opened when navigating to enter magic code step[/+]melvin-bot commentedon Nov 15, 2024
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Nov 15, 2024
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.62-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2024-11-22. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Nov 15, 2024
@Ollyws @twisterdotcom @Ollyws The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]
twisterdotcom commentedon Nov 22, 2024
Payment Summary:
twisterdotcom commentedon Nov 22, 2024
Waiting on the checklist now @Ollyws.
[-][HOLD for payment 2024-11-22] [$250] Contact method - Keyboard not opened when navigating to enter magic code step[/-][+][Awaiting checklist] [$250] Contact method - Keyboard not opened when navigating to enter magic code step[/+]bernhardoj commentedon Nov 22, 2024
Requested in ND.
JmillsExpensify commentedon Nov 25, 2024
$250 approved for @bernhardoj
Ollyws commentedon Nov 25, 2024
BugZero Checklist:
Bug classification
Source of bug:
Where bug was reported:
Who reported the bug:
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment: https://github.com/Expensify/App/pull/49445/files#r1857315081
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion:
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
Regression Test Proposal Template
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue:
Regression Test Proposal
Precondition:
Test:
Do we agree 👍 or 👎
Ollyws commentedon Nov 25, 2024
Requested in ND.
garrettmknight commentedon Nov 26, 2024
$250 approved for @Ollyws