-
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 for payment 2023-09-29] [HOLD for payment 2023-09-27] Web - Pressing CTRL+SHIFT+K opens Send message page with random URL params #27710
Comments
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open
|
Triggered auto assignment to @jasperhuangg ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.Web - When pressing CTRL+SHIFT+K, the "Send Message" page opens with random URL parameters. What is the root cause of that problem?The root cause is from beta feature.
The app works correctly when the beta policy room feature is enabled. However, for normal users, it navigates to "new/chat," which doesn't exist due to the following code: App/src/pages/NewChatSelectorPage.js Lines 38 to 59 in 6be8fca
What changes do you think we should make in order to solve the problem?To address this issue, I propose modifying this code:
Navigation.navigate(Permissions.canUsePolicyRooms(this.props.betas) ? ROUTES.NEW_CHAT : ROUTES.NEW);
// or
Navigation.navigate(ROUTES.NEW); What alternative solutions did you explore? (Optional)N/A |
@Pluto0104's proposal (2nd solution) looks good to me. This is consistent with navigating from FAB. App/src/pages/home/sidebar/SidebarScreen/FloatingActionButtonAndPopover.js Lines 184 to 186 in 6be8fca
|
Ah thank you for the proposals guys. I already started work on this before seeing them. Please only comment on issues that have the |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.71-12 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-09-27. 🎊 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:
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.72-11 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-09-29. 🎊 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:
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
|
@jasperhuangg, @situchan Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
Triggered auto assignment to @peterdbarkerUK ( |
Bug0 Triage Checklist (Main S/O)
|
@peterdbarkerUK, @jasperhuangg, @situchan Still overdue 6 days?! Let's take care of this! |
Double checking what steps to follow in this case (for my own paper trail) |
Confirmed that only the reporter gets paid here, I'm sorry. As @jasperhuangg said: Please only comment on issues that have the Bug and External labels applied if you want your proposals to be reviewed/accepted. Thanks! I made a mistake with the payment, sending it as a bonus tied to this job instead of creating a new one. I've updated the other issue |
@peterdbarkerUK I think C+ payment for PR review is pending. Can you please check? |
@peterdbarkerUK accepted. thanks |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Action Performed:
Note: make sure you don't have policy room permission
Expected Result:
The URL should show /new without any params (just like when we open it from FAB)
Actual Result:
The URL contains some random params
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.3.71.5
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
Notes/Photos/Videos: Any additional supporting documentation
Screen.Recording.2023-09-18.at.01.07.11.mov
Recording.4590.mp4
Expensify/Expensify Issue URL:
Issue reported by: @bernhardoj
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1694970567497589
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: