Repository navigation
[HOLD for payment 2024-02-19] [$500] [Wave 8] [Ideal Nav] The color of Status Bar (top part of the background) is not consistent #35632
Description
Activity
Triggered auto assignment to @abekkala (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.- changed the title
[-]The color of Status Bar (top part of the background) is not consistent[/-][+][Wave 8] [Ideal Nav] The color of Status Bar (top part of the background) is not consistent[/+]on Feb 2, 2024 - moved this to Release 1: Ideal Nav & Collect Simplfied Profile, Members, Categories, Workflows (approvals) in [#whatsnext] Wave 08 - Collect Plan Admins
on Feb 2, 2024 - changed the title
[-][Wave 8] [Ideal Nav] The color of Status Bar (top part of the background) is not consistent[/-][+][$500] [Wave 8] [Ideal Nav] The color of Status Bar (top part of the background) is not consistent[/+]on Feb 2, 2024 Job added to Upwork: https://www.upwork.com/jobs/~01f7200068e359bb73
Triggered auto assignment to Contributor-plus team member for initial proposal review - @rushatgabhane (
External)Please hold a little bit before posting proposals until I confirm that this issue is handled independently (there is a possibility that this issue is combined with this issue)
Reacted by Rushat Gabhane17 remaining items
@hayata-suenaga It's not fixed yet for the home page #35632 (comment)
@kosmydel could you check this comment when you have time please? 🙇
@kosmydel could you check this comment when you have time please? 🙇
Changing this in config broke the android insets. That's why I haven't changed it. Here is more details:
#35564 (comment)- changed the title
[-][$500] [Wave 8] [Ideal Nav] The color of Status Bar (top part of the background) is not consistent[/-][+][HOLD for payment 2024-02-19] [$500] [Wave 8] [Ideal Nav] The color of Status Bar (top part of the background) is not consistent[/+]on Feb 12, 2024 Reviewinglabel has been removed, please complete the "BugZero Checklist".The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.39-8 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-02-19. 🎊
For reference, here are some details about the assignees on this issue:
- @rushatgabhane requires payment through NewDot Manual Requests
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.
- [@abekkala] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:
@kosmydel could you check #35632 (comment) when you have time please? 🙇
Changing this in config broke the android insets. That's why I haven't changed it. Here is more details:
#35564 (comment)@kosmydel Thank you for reminding me of that. Are you working on this in a separate issue or should I create a new issue for you?
@kosmydel Thank you for reminding me of that. Are you working on this in a separate issue or should I create a new issue for you?
I can have a look at this, but I found a PR (#34409) that addresses a mWeb status bar issue. The author of the PR suggests that he found a solution for that. In case this doesn't solve our problem, I can surely investigate it.
Reacted by Hayata Suenagaokay let's see if the PR will solve the issue 👍
Unfortunately there was other PR on which my suggested changes depends #34637 to fully solve the problem and that PR had some blockers (might have been resolved now) so i decided not to include the suggested change in my PR
Action Performed:
Expected Result:
The color should be consistent
Actual Result:
The colors are different across different pages
Workaround:
N/A
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
screenshots -> #33280 (comment)
View all open jobs on GitHub
Upwork Automation - Do Not Edit