-
Notifications
You must be signed in to change notification settings - Fork 3.2k
Expensify logo has same redirection as "Inbox" #60428
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
Comments
Triggered auto assignment to @lakchote ( |
💬 A slack conversation has been started in #expensify-open-source |
👋 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:
|
Looks like it could be related to [Desktop Navigation] Add a responsive LHB cc @mountiny |
I think the both have the same Navigation.navigate() redirection, perhaps we should change it to WS switcher. Posting a proposal soon if this goes external... |
ProposalPlease re-state the problem that we are trying to solve in this issue.Expensify logo has same redirection as "Inbox" What is the root cause of that problem?We use pressable Expensify Logo here and on click execute App/src/components/Navigation/NavigationTabBar/index.tsx Lines 208 to 220 in 717b77a
What changes do you think we should make in order to solve the problem?Use
What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?N/A What alternative solutions did you explore? (Optional)N/A |
Hey, this is expected behaviour, it is in line with the design doc |
This issue is not reproducible on the latest main, can someone verify |
ProposalPlease re-state the problem that we are trying to solve in this issue.Expensify logo has same redirection as "Inbox" What is the root cause of that problem?We are clearly redirecting to the App/src/components/Navigation/NavigationTabBar/index.tsx Lines 212 to 213 in 717b77a
Perhaps this is the root cause What changes do you think we should make in order to solve the problem?Instead Replace this line:
with, onPress={() => Navigation.navigate(ROUTES.WORKSPACE_SWITCHER)} What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?NA What alternative solutions did you explore? (Optional)NA ResultReminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job. |
Since this is deployblocker, i can help raise a quick PR. cc: @lakchote |
Thank you for clarifying! You are right, it's expected given what has been written in the design doc here. Closing the issue. |
Thanks! We will updated the test rail cases as part of the proejct |
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.1.29-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
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:
User expects the 2 buttons to have different redirections, perhaps the E button should lead to WS switcher
Actual Result:
Both buttons have the same redirection
Workaround:
Unknown
Platforms:
Select the officially supported platforms where the issue was reproduced:
Platforms Tested:
On which of our officially supported platforms was this issue tested:Screenshots/Videos
Add any screenshot/video evidence
Bug6805085_1744896253003.Same_redirection_for_2_different_buttons.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: