-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[$125] Workspace switcher - Back button returns to Inbox when creating new workspace in Search page #47562
Comments
Triggered auto assignment to @greg-schroeder ( |
We think that this bug might be related to #vip-vsp |
I'm not sure this is the expected behavior, so we should confirm on slack. I think the right label to apply here would be DeployBlockerCash and not DeployBlocker |
Triggered auto assignment to @stitesExpensify ( |
I don't think this should block the App deploy either, cc @chiragsalian |
👋 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:
|
Job added to Upwork: https://www.upwork.com/jobs/~017ecb2af50a3c8e0d |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @parasharrajat ( |
Edited by proposal-police: This proposal was edited at 2024-08-19 15:40:42 UTC. ProposalPlease re-state the problem that we are trying to solve in this issue.Workspace switcher - Back button returns to Inbox when creating new workspace in Search page What is the root cause of that problem?
What changes do you think we should make in order to solve the problem?We should check if the topmost central pane is search screen, if true we will update the active route. onPress={() => {
let activeRoute = Navigation.getActiveRouteWithoutParams();
const topmostCentralPaneRoute = getTopmostCentralPaneRoute(navigationRef.getRootState() as State<RootStackParamList>);
if (topmostCentralPaneRoute?.name === SCREENS.SEARCH.CENTRAL_PANE) {
const currentSearchParams = getCurrentSearchParams();
if (currentSearchParams) {
const {q, ...rest} = currentSearchParams;
const policy = PolicyUtils.getPolicy(currentSearchParams?.policyIDs);
activeRoute = ROUTES.SEARCH_CENTRAL_PANE.getRoute({query: q, ...rest, policyIDs: policy ? currentSearchParams?.policyIDs : undefined});
}
activeRoute = ROUTES.SEARCH_CENTRAL_PANE.getRoute({query: CONST.SEARCH.TAB.EXPENSE.ALL});
}
interceptAnonymousUser(() => App.createWorkspaceWithPolicyDraftAndNavigateToIt('', '', false, false, activeRoute));
}} We can create a util function to check What alternative solutions did you explore? (Optional)We can update the ResultMonosnap.screencast.2024-08-20.01-03-34.mp4 |
Thanks @parasharrajat, let me know where you land |
Still debugging this. |
Sounds good |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
Rajat is still debugging |
Couldn't spend time on it yesterday. I will analyze this further on the weekend. |
@parasharrajat @greg-schroeder this issue is now 4 weeks old, please consider:
Thanks! |
Rajat will get to this during the week |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
Bump @parasharrajat :) |
Bump @parasharrajat |
@greg-schroeder Thanks for the bump. I looked into the proposal and issue. It seems to be much more involved than I expected. I am worried about touching the navigation code which affects the whole app. Let me see what is best here. |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
@parasharrajat, @greg-schroeder Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
Proposal Updated
|
Still in proposal review |
@parasharrajat, @greg-schroeder 6 days overdue. This is scarier than being forced to listen to Vogon poetry! |
#vip-vsb is now fully paused/closed, so I'm going to close this as it doesn't really fit in #newdot-quality or any other active project. |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Version Number: 9.0.21-0
Reproducible in staging?: Y
Reproducible in production?: N
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): [email protected]
Issue reported by: Applause - Internal Team
Action Performed:
Expected Result:
App will return to Search page with workspace switcher panel opened
Actual Result:
App returns to Inbox page with workspace switcher panel opened
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6573301_1723754483501.20240816_042927.1.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @parasharrajatThe text was updated successfully, but these errors were encountered: