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 2025-01-24] [$250] IOS - Empty screen seen when navigating back from workspace description the second time #53589
Version Number: 9.0.71-0 Reproducible in staging?: Y Reproducible in production?: Y If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Y 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):nathanmulugetatesting+2338@gmail.com Issue reported by: Applause - Internal Team
Action Performed:
Open IOS hybrid app
Create a workspace give it a custom description
Navigate to the inbox
Open workspace chat
Tap on the custom description to navigate to description setting of the workspace
Navigate back twice by tapping on the top left back icon until you reach workspace editor page
Tap on Workspace chat
Re do step 5
Tap on the top corner back icon or swipe from left to right
Expected Result:
Empty screen does not get shown
Actual Result:
Empty screen gets shown and the workspace profile settings page animation is wrong, it slides from right to left after the empty screen has been shown first
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Android: Standalone
Android: HybridApp
Android: mWeb Chrome
iOS: Standalone
iOS: HybridApp
iOS: mWeb Safari
MacOS: Chrome / Safari
MacOS: Desktop
Screenshots/Videos
Add any screenshot/video evidenceBug6684551_1733335793079.ScreenRecording_12-04-2024_21-02-36_1.1.mp4
changed the title [-] IOS - Empty screen seen when navigating back from workspace description the second time[/-][+][$250] IOS - Empty screen seen when navigating back from workspace description the second time[/+]on Dec 6, 2024
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.86-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@ikevin127 / @ishpaul777@muttmuure@ikevin127 / @ishpaul777 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]
[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: N/A.
[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.
[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
Test 1:
Create a workspace give it a custom description (WS Settings > Workspage profile > Description).
Navigate to inbox.
Open workspace chat.
Verify that click / tap on the report's custom description welcome text doesn't do anything.
Verify that click / tap on the report header custom description text opens the report details page (RHP).
Test 2:
Start a #room chat and give it a custom description.
Open the chat.
Verify that click / tap on the report's custom description welcome text doesn't do anything.
Verify that click / tap on the report header custom description text opens the report details page (RHP).
Test 3:
Navigate to an existing invoice room.
Give the invoice room a custom description.
Verify that click / tap on the report's custom description welcome text doesn't do anything.
Verify that click / tap on the report header custom description text opens the report details page (RHP).
Activity
melvin-bot commentedon Dec 4, 2024
Triggered auto assignment to @muttmuure (
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 Dec 6, 2024
Job added to Upwork: https://www.upwork.com/jobs/~021865096772528155887
[-] IOS - Empty screen seen when navigating back from workspace description the second time[/-][+][$250] IOS - Empty screen seen when navigating back from workspace description the second time[/+]melvin-bot commentedon Dec 6, 2024
Triggered auto assignment to Contributor-plus team member for initial proposal review - @ishpaul777 (
External)ikevin127 commentedon Dec 7, 2024
61 remaining items
melvin-bot commentedon Jan 17, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Jan 17, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.86-3 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 2025-01-24. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Jan 17, 2025
@ikevin127 / @ishpaul777 @muttmuure @ikevin127 / @ishpaul777 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]
mvtglobally commentedon Jan 18, 2025
Issue not reproducible during KI retests. (Second week)
ikevin127 commentedon Jan 25, 2025
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: #37165 (commit comment).
[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: N/A.
[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.
[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
Test 1:
Test 2:
Test 3:
Do we agree 👍 or 👎.
cc @muttmuure for payments
melvin-bot commentedon Jan 27, 2025
@deetergp, @muttmuure, @ikevin127, @ishpaul777 Whoops! This issue is 2 days overdue. Let's get this updated quick!
ishpaul777 commentedon Jan 27, 2025
just waiting payment here
ikevin127 commentedon Jan 27, 2025
cc @muttmuure for payments (tagged on Slack thread as well)
mallenexpensify commentedon Jan 28, 2025
Contributor: @ikevin127 paid $250 via Upwork
Contributor+: @ishpaul777 paid $250 via Upwork
Test case - https://github.com/Expensify/Expensify/issues/465111
Think I got it all, thanks!