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
[HOLD for payment 2024-08-09] [$250] Workspace - App back button overlaps with the status bar on not here page #46183
Version Number: 9.0.12-0 Reproducible in staging?: y Reproducible in production?: no If this was caught during regression testing, add the test name, ID and link from TestRail: n/a Email or phone of affected tester (no customers): Logs:https://stackoverflow.com/c/expensify/questions/4856 Expensify/Expensify Issue URL: Issue reported by: applause internal team Slack conversation:
Action Performed:
Launch New Expensify app.
Create a new workspace.
Go to Workspace settings > More features > Report fields.
Toggle on Report fields and tap Upgrade to upgrade to Control plan.
Go to Troubleshoot > Clear cache and restart > Reset and refresh.
Go to LHN and check that #admins room is present.
Delete the workspace.
Go to the now archieved #admins room.
Tap on the "here" link.
Expected Result:
App back button will not overlap with the status bar on not here page.
Actual Result:
App back button overlaps with the status bar on not here page.
Workaround:
unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
👋 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.
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.15-9 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
[@rushatgabhane] The PR that introduced the bug has been identified. Link to the PR:
[@rushatgabhane] 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:
[@rushatgabhane] A discussion in #expensify-bugs 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:
[@rushatgabhane] Determine if we should create a regression test for this bug.
[@rushatgabhane] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
[@stephanieelliott] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:
Activity
melvin-bot commentedon Jul 25, 2024
Triggered auto assignment to @stephanieelliott (
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 Jul 25, 2024
Triggered auto assignment to @Julesssss (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.github-actions commentedon Jul 25, 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:
m-natarajan commentedon Jul 25, 2024
We think that this bug might be related to #wave-collect - Release 1
28 remaining items
melvin-bot commentedon Aug 2, 2024
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.15-9 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-08-09. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Aug 2, 2024
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
stephanieelliott commentedon Aug 6, 2024
Hey @bernhardoj @rushatgabhane seems like #46646 may be a regression -- can you take a look?
rushatgabhane commentedon Aug 6, 2024
hey, it looks like it's unrelated to the PR
stephanieelliott commentedon Aug 7, 2024
Got it! Ok thanks for checking.
bernhardoj commentedon Aug 9, 2024
Requested in ND for the payment today.
JmillsExpensify commentedon Aug 9, 2024
Can I get a payment summary?
melvin-bot commentedon Aug 9, 2024
Payment Summary
Upwork Job
BugZero Checklist (@stephanieelliott)
stephanieelliott commentedon Aug 10, 2024
Summarizing payment on this issue:
Upwork job is here: https://www.upwork.com/jobs/~014856468550d7e9c5
JmillsExpensify commentedon Aug 10, 2024
$250 approved for each of @bernhardoj and @rushatgabhane