Skip to content
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

Workspace - Back button returns to the same workspace page after upgrading to Control #46450

Closed
6 tasks done
m-natarajan opened this issue Jul 29, 2024 · 13 comments
Closed
6 tasks done
Assignees
Labels
Bug Something is broken. Auto assigns a BugZero manager. DeployBlockerCash This issue or pull request should block deployment Engineering Hourly KSv2

Comments

@m-natarajan
Copy link

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


Issue found when validating #45730
Version Number: 9.0.14-1
Reproducible in staging?: y
Reproducible in production?: n
If this was caught during regression testing, add the test name, ID and link from TestRail:
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:

  1. Go to staging.new.expensify.com
  2. Create a new workspace.
  3. Go to More features.
  4. Toggle on Report fields.
  5. Click Upgrade.
  6. Click Got it, thanks.
  7. Click on the app back button.

Expected Result:

App will return to workspace list page (previous page).

Actual Result:

App returns to the same workspace editor page, which is from More features back to More features page again.

On prod, the back button works correctly as it returns from Profile to More features page.

Workaround:

unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Bug6556599_1722282753369.20240730_035010.mp4

View all open jobs on GitHub

@m-natarajan m-natarajan added DeployBlockerCash This issue or pull request should block deployment Daily KSv2 Bug Something is broken. Auto assigns a BugZero manager. DeployBlocker Indicates it should block deploying the API labels Jul 29, 2024
Copy link

melvin-bot bot commented Jul 29, 2024

Triggered auto assignment to @isabelastisser (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.

Copy link

melvin-bot bot commented Jul 29, 2024

Triggered auto assignment to @aldo-expensify (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

@github-actions github-actions bot added Engineering Hourly KSv2 and removed Daily KSv2 labels Jul 29, 2024
Copy link
Contributor

👋 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:

  1. Identify the pull request that introduced this issue and revert it.
  2. Find someone who can quickly fix the issue.
  3. Fix the issue yourself.

@chiragsalian
Copy link
Contributor

Doesn't look web-e related. removing deployblocker label.

@chiragsalian chiragsalian removed the DeployBlocker Indicates it should block deploying the API label Jul 29, 2024
@aldo-expensify
Copy link
Contributor

I see that in production it takes you automatically to the workspace's Profile page after the upgrade:

Screen.Recording.2024-07-29.at.2.49.24.PM.mov

This doesn't happen in the recording from this issue

@aldo-expensify
Copy link
Contributor

I think this is happening because of this PR: https://github.com/Expensify/App/pull/45730/files

@aldo-expensify
Copy link
Contributor

cc @allroundexperts @rushatgabhane

@aldo-expensify
Copy link
Contributor

I think this works well if you scrolled down to find Report fields inside More features, because then the Back button will scroll you down to where you were when you clicked Report fields and a second click will take you out to the Profile:

Screen.Recording.2024-07-29.at.3.06.01.PM.mov

but, if you didn't scroll down to find the Report fields, then the first press on the back button will not move the scrollbar making it look like it did nothing:

Screen.Recording.2024-07-29.at.3.06.47.PM.mov

@aldo-expensify
Copy link
Contributor

aldo-expensify commented Jul 29, 2024

I think the easiest fix is that we should NOT do any navigation when we upgrade in this flow. We are currently scrolling up, but what for?

image

@aldo-expensify
Copy link
Contributor

Creating a revert here since I'm not sure what is the right way to fix this and the transition also doesn't look good: #46460

@allroundexperts
Copy link
Contributor

Hm... Is a revert really needed here? Asking because this PR fixes issues which might be of greater importance than this bug.

@aldo-expensify
Copy link
Contributor

aldo-expensify commented Jul 29, 2024

Hm... Is a revert really needed here? Asking because this PR fixes issues which might be of greater importance than this bug.

Do you have some examples? I'm just suggesting a revert because I didn't see it fixing something of importance, I don't have a clear solution for this deploy blocker, and the animation here looks broken #45730 (comment)

Feel free to suggest a solution without reverting. Ah, the revert was merged, too late.

@aldo-expensify
Copy link
Contributor

Reverted and tested: #46460

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something is broken. Auto assigns a BugZero manager. DeployBlockerCash This issue or pull request should block deployment Engineering Hourly KSv2
Projects
None yet
Development

No branches or pull requests

5 participants