-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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 for payment 2023-11-02] [$500] Web - Room - Search list can be opened with CMD + K in public room as anonymous user #28249
Comments
Triggered auto assignment to @zanyrenney ( |
Bug0 Triage Checklist (Main S/O)
|
ProposalPlease re-state the problem that we are trying to solve in this issue.Fixing redirect issue with using shortcut What is the root cause of that problem?The problem is we are not checking if user is App/src/libs/Navigation/AppNavigator/AuthScreens.js Lines 182 to 191 in 3402597
unlike we are checking on App/src/pages/home/sidebar/SidebarLinks.js Line 173 in 3402597
What changes do you think we should make in order to solve the problem?We should also check this condition on shortcut click. we can update this function to like we are checking on search icon click. Modal.close(Session.checkIfActionIsAllowed(() => {
if (Navigation.isActiveRoute(ROUTES.SEARCH)) {
return;
}
return Navigation.navigate(ROUTES.SEARCH);
})); and we should update this chat shortcut listener also to respect anonymous users. and we should add early return condition here to avoid re-navigating to sign-in modal page. if (Navigation.isActiveRoute(ROUTES.SIGN_IN_MODAL)) {
return
}; ResultScreen.Recording.2023-09-26.at.5.50.52.PM.movWhat alternative solutions did you explore? (Optional)We can disable shortcut for anonymous users |
adding external. |
Job added to Upwork: https://www.upwork.com/jobs/~01e7ac225db079b27f |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @0xmiroslav ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.
What is the root cause of that problem?
What changes do you think we should make in order to solve the problem?
What alternative solutions did you explore? (Optional)
Result:Solution 1: Screencast.from.29-08-2023.17.31.39.webm |
@zanyrenney, @0xmiroslav Eep! 4 days overdue now. Issues have feelings too... |
@0xmiroslav please can you review the proposals? |
reviewing today |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
Triggered auto assignment to @AndrewGable, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
@0xmiroslav we need to cover the user entering the URL directly also? |
I think that can be separate issue. None of direct urls seem to work correctly for me |
got it Thanks let me raise it separately. |
@0xmiroslav ya yes we need to hide that as well. |
📣 @0xmiroslav 🎉 An offer has been automatically sent to your Upwork account for the Reviewer role 🎉 Thanks for contributing to the Expensify app! |
📣 @kushu7 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Offer link |
@0xmiroslav PR is ready for review. cc @AndrewGable |
I think we should hold this issue until this regression is fixed. This happens on main right now. |
Let's put this on hold for #29341 |
@0xmiroslav This issue is fixed by reverting those related PR. #29341 (comment) |
yes, let's remove hold. |
Based on my calculations, the pull request did not get merged within 3 working days of assignment. Please, check out my computations here:
On to the next one 🚀 |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.91-8 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 2023-11-02. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
For reference, here are some details about the assignees on this issue: |
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
@0xmiroslav @zanyrenney it was on hold i guess 🤔 |
The PR was approved (both C+ and engineer) quickly after removing hold. |
Yes this was on hold for 10 days, it was reviewed/merged in 3 days after the hold. cc @zanyrenney |
@zanyrenney Andrew confirmed. Thanks |
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:
Expected Result:
Login menu will open when using the shortcut CMD + K, just like when clicking on the search icon in Step 2.
Actual Result:
The search list is opened when using CMD + K.
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: v1.3.74-2
Reproducible in staging?: Y
Reproducible in production?: Y
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
Notes/Photos/Videos: Any additional supporting documentation
Bug6214634_20230926_023604.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause-Internal Team
Slack conversation: @
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: