-
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
[HOLD] Restricted access - Redirection does not work #12676
Comments
Triggered auto assignment to @mateocole ( |
QA team is Failing steps in TestRail https://expensify.testrail.io/index.php?/tests/view/2936076 |
Triggered auto assignment to @alex-mechler ( |
Having an engineer confirm this is something I can mark external |
Yup, looks like something broke here. Since this is just routing this can go external |
Current assignee @mateocole is eligible for the External assigner, not assigning anyone new. |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @mollfpr ( |
Triggered auto assignment to @marcaaron ( |
@kbecciv I logged in my account. but I got this screen when I visit https://staging.new.expensify.com/r/6821704960193694. |
@mateocole were you able to reproduce on 2022-11-15_13-41-03.mp4Couple thoughts...
|
Same as @marcaaron I can't reproduce it. I feel like this is a regression from this PR where it should redirect to the concierge chat. But the issue #11982 is not stated needs to redirect to the concierge chat. |
Hmm I am so confused about that PR you linked. If a chat doesn't exist in storage yet we are just redirecting randomly? Why does the report not exist? Do we try to access it from the server? I'm totally lost, but the HOC solution seems very strange to me. @Beamanator please share your thoughts here. @kbecciv Where does the expectation that we should redirect to the Concierge chat come from? Is it an existing TC? @mateocole I think we need to bring this one into #bug-zero to resolve. |
@marcaaron Here is the TR link for Restricted access part |
Yes, currently we do dismiss the modal. The expected result from this #11982 is not stated redirecting to the concierge.
When we try to access other account report IDs (where the current account is not part of the group/room/workspace), the report data is not available in the storage.
We don't fetch the targeted report ID in the
We handle the same things for the 3 pages, so I think it's okay to create a HOC for that. |
Oh shoot I totally thought this was one of the ones holding on navigation reboot, sorry - I will jump into a plan for this tomorrow, may see if someone else will take it off my plate too 😅 |
Still pretty low priority, though some higher priority projects are finishing up soon so will try to get to this one mid march |
Going to be OOO, reassigning |
On hold for some higher priority tasks |
still quite low priority |
Triggered auto assignment to @joekaufmanexpensify ( |
Bug0 Triage Checklist (Main S/O)
|
Reassigning @joekaufmanexpensify I think we need to reevaluate if this is still a bug / if we need to fix something here please 🙏 |
Sounds good, I'll take a look today! |
@Beamanator I tested this, and when I try and navigate to the links in OP, I get the "Hm, it's not here" error. It seems like this is one of the expected behavior options discussed here. And then the user has the option to redirect to the home page. |
Personally, I feel like this is fine. I don't think it'll be common that someone will be copying an actual report they don't have access to. What feels much more likely to me is that someone would copy a report they do have access to, but with a typo. And the existing error sufficiently communicates that they did something wrong. At which point, they'll likely realize, and correct the typo, or navigate to the home page using the button on the screen. If you agree, then I think we're all set to close this one! |
@joekaufmanexpensify That definitely sounds legit to me! |
Cool cool. Closing as this has been fixed by the navigation reboot! |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Action Performed:
https://staging.new.expensify.com/r/6821704960193694/details
https://staging.new.expensify.com/r/6821704960193694/participants
https://staging.new.expensify.com/r/6821704960193694/settings
Expected Result:
You should be redirected to the concierge conversation
Actual Result:
Redirection does not work
Workaround:
Unknown
Platform:
Where is this issue occurring?
Version Number: 1.2.27.0
Reproducible in staging?: Yes
Reproducible in production?: Yes
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Bug5816583_Recording__2858.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: