redirect `Anon` user to sign in page on shortcut use #29323

kushu7 · 2023-10-11T14:36:31Z

Details

Fixing redirect issue with using shortcut CMD + K or CMD + SHIFT + K in public room as anonymous user

Fixed Issues

$ #28249
PROPOSAL: #28249 (comment)

Tests

Same as QA Steps

Verify that no errors appear in the JS console

Offline tests

Same as QA Steps

QA Steps

Go to a public room as an anonymous user like: https://staging.new.expensify.com/r/6551927535024433.
Use the shortcut CMD + K, verify that login modal appears.
Close the login menu.
Use the shortcut CMD + SHIFT + K, verify that login modal appears.

Verify that no errors appear in the JS console

PR Author Checklist

I linked the correct issue in the ### Fixed Issues section above
I wrote clear testing steps that cover the changes made in this PR
- I added steps for local testing in the Tests section
- I added steps for the expected offline behavior in the Offline steps section
- I added steps for Staging and/or Production testing in the QA steps section
- I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
- I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
- I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
I included screenshots or videos for tests on all platforms
I ran the tests on all platforms & verified they passed on:
- Android: Native
- Android: mWeb Chrome
- iOS: Native
- iOS: mWeb Safari
- MacOS: Chrome / Safari
- MacOS: Desktop
I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
I followed proper code patterns (see Reviewing the code)
- I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
- I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
- I verified that comments were added to code that is not self explanatory
- I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
- I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
  - If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
- I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
- I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
- I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
- I verified the JSDocs style guidelines (in STYLE.md) were followed
If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
I followed the guidelines as stated in the Review Guidelines
I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
I verified that if a function's arguments changed that all usages have also been updated correctly
If a new component is created I verified that:
- A similar component doesn't exist in the codebase
- All props are defined accurately and each prop has a /** comment above it */
- The file is named correctly
- The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
- The only data being stored in the state is data necessary for rendering and nothing else
- If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
- For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
- Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
- All JSX used for rendering exists in the render method
- The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
If any new file was added I verified that:
- The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
If a new CSS style is added I verified that:
- A similar style doesn't already exist
- The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG))
If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

WhatsApp.Video.2023-10-11.at.10.06.25.PM.1.mp4

Android: mWeb Chrome

android-chrome.mp4

iOS: Native

ios.mp4

iOS: mWeb Safari

mweb-safari.mp4

MacOS: Chrome / Safari

web.mov

MacOS: Desktop

desktop.mov

melvin-bot · 2023-10-11T16:41:28Z

@0xmiroslav Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

0xmiros · 2023-10-12T16:37:03Z

I found weird bug on main

Repro step:

Press Ctrk+K
Expects to open Search page but nothing happens (BUG)
Open FAB menu
Close FAB menu by clicking anywhere outside
Search page opens this time (BUG)

Screen.Recording.2023-10-12.at.6.35.41.PM.mov

0xmiros · 2023-10-12T16:51:29Z

Confirmed this regression came from #27639.
Reverting #27639 fixes it.

…hortcut-issue

0xmiros · 2023-10-22T08:06:36Z

Reviewer Checklist

I have verified the author checklist is complete (all boxes are checked off).
I verified the correct issue is linked in the ### Fixed Issues section above
I verified testing steps are clear and they cover the changes made in this PR
- I verified the steps for local testing are in the Tests section
- I verified the steps for Staging and/or Production testing are in the QA steps section
- I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
- I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
I checked that screenshots or videos are included for tests on all platforms
I included screenshots or videos for tests on all platforms
I verified tests pass on all platforms & I tested again on:
- Android / native
- Android / Chrome
- iOS / native
- iOS / Safari
- MacOS / Chrome / Safari
- MacOS / Desktop
If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
I verified proper code patterns were followed (see Reviewing the code)
- I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
- I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
- I verified that comments were added to code that is not self explanatory
- I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
- I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
- I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
- I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
- I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
- I verified the JSDocs style guidelines (in STYLE.md) were followed
If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
I verified that this PR follows the guidelines as stated in the Review Guidelines
I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
If a new component is created I verified that:
- A similar component doesn't exist in the codebase
- All props are defined accurately and each prop has a /** comment above it */
- The file is named correctly
- The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
- The only data being stored in the state is data necessary for rendering and nothing else
- For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
- Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
- All JSX used for rendering exists in the render method
- The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
If any new file was added I verified that:
- The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
If a new CSS style is added I verified that:
- A similar style doesn't already exist
- The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)
If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

web.mov

Mobile Web - Chrome

mchrome.mov

Mobile Web - Safari

msafari.mov

Desktop

desktop.mov

iOS

ios.mov

Android

android.mov

0xmiros

LGTM!

AndrewGable · 2023-10-23T18:18:52Z

Conflicts!

0xmiros · 2023-10-23T18:23:29Z

src/libs/actions/Session/index.js

@@ -87,6 +87,9 @@ function signOutAndRedirectToSignIn() {
        signOut();
        redirectToSignIn();
    } else {
+        if (Navigation.isActiveRoute(ROUTES.SIGN_IN_MODAL)) {
+            return;
+        }


@kushu7 This file is migrated into .ts

@0xmiroslav conflicts resolved

cc @AndrewGable

…hortcut-issue

AndrewGable · 2023-10-24T21:20:17Z

@0xmiroslav - Were you able to run through the tests once more before approving? Just wanted to double check, thanks.

0xmiros · 2023-10-25T05:44:58Z

@0xmiroslav - Were you able to run through the tests once more before approving? Just wanted to double check, thanks.

yes, tested

OSBotify · 2023-10-25T16:20:17Z

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

OSBotify · 2023-10-25T16:59:08Z

🚀 Deployed to staging by https://github.com/AndrewGable in version: 1.3.91-0 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅

OSBotify · 2023-10-26T22:41:09Z

🚀 Deployed to production by https://github.com/marcaaron in version: 1.3.91-8 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅

redirect anon user to sign in page on shortcut use

6b8bdc0

kushu7 marked this pull request as ready for review October 11, 2023 16:41

kushu7 requested a review from a team as a code owner October 11, 2023 16:41

melvin-bot bot requested review from 0xmiros and removed request for a team October 11, 2023 16:41

merged main

51ce9ab

Merge remote-tracking branch 'origin/main' into fix-28249-anonymous-s…

7a62bb1

…hortcut-issue

kushu7 mentioned this pull request Oct 22, 2023

[HOLD for payment 2023-11-02] [$500] Web - Room - Search list can be opened with CMD + K in public room as anonymous user #28249

Closed

6 tasks

0xmiros approved these changes Oct 22, 2023

View reviewed changes

melvin-bot bot requested a review from AndrewGable October 22, 2023 08:06

AndrewGable previously approved these changes Oct 23, 2023

View reviewed changes

0xmiros reviewed Oct 23, 2023

View reviewed changes

Merge remote-tracking branch 'origin/main' into fix-28249-anonymous-s…

8fad6f3

…hortcut-issue

kushu7 dismissed AndrewGable’s stale review via 8fad6f3 October 23, 2023 21:30

0xmiros approved these changes Oct 23, 2023

View reviewed changes

melvin-bot bot requested a review from AndrewGable October 23, 2023 21:31

situchan mentioned this pull request Oct 25, 2023

Refactor/16226/auth screens components migration to functional #27764

Merged

58 tasks

AndrewGable approved these changes Oct 25, 2023

View reviewed changes

AndrewGable merged commit 3c9572d into Expensify:main Oct 25, 2023
16 checks passed

OSBotify mentioned this pull request Oct 25, 2023

Deploy Checklist: New Expensify 2023-10-25 #30365

Closed

99 tasks

kushu7 deleted the fix-28249-anonymous-shortcut-issue branch October 25, 2023 16:30

lanitochka17 mentioned this pull request Oct 25, 2023

Room - App crashes when using CMD+K shortcut in public room as a logged out user #30389

Closed

6 tasks

ishpaul777 mentioned this pull request Oct 28, 2023

[HOLD for payment 2023-11-27] [$250] Dev: Web - Search page is not opening with transition when navigating with keyboard shortcut while on sign in page as anonymous user #29112

Closed

6 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

redirect `Anon` user to sign in page on shortcut use #29323

redirect `Anon` user to sign in page on shortcut use #29323

kushu7 commented Oct 11, 2023 •

edited

Loading

melvin-bot bot commented Oct 11, 2023

0xmiros commented Oct 12, 2023

0xmiros commented Oct 12, 2023

0xmiros commented Oct 22, 2023 •

edited

Loading

0xmiros left a comment

AndrewGable commented Oct 23, 2023

0xmiros Oct 23, 2023

kushu7 Oct 23, 2023

AndrewGable commented Oct 24, 2023

0xmiros commented Oct 25, 2023

OSBotify commented Oct 25, 2023

OSBotify commented Oct 25, 2023

OSBotify commented Oct 26, 2023

redirect Anon user to sign in page on shortcut use #29323

redirect Anon user to sign in page on shortcut use #29323

Conversation

kushu7 commented Oct 11, 2023 • edited Loading

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

melvin-bot bot commented Oct 11, 2023

0xmiros commented Oct 12, 2023

0xmiros commented Oct 12, 2023

0xmiros commented Oct 22, 2023 • edited Loading

Reviewer Checklist

Screenshots/Videos

0xmiros left a comment

Choose a reason for hiding this comment

AndrewGable commented Oct 23, 2023

0xmiros Oct 23, 2023

Choose a reason for hiding this comment

kushu7 Oct 23, 2023

Choose a reason for hiding this comment

AndrewGable commented Oct 24, 2023

0xmiros commented Oct 25, 2023

OSBotify commented Oct 25, 2023

OSBotify commented Oct 25, 2023

OSBotify commented Oct 26, 2023

redirect `Anon` user to sign in page on shortcut use #29323

redirect `Anon` user to sign in page on shortcut use #29323

kushu7 commented Oct 11, 2023 •

edited

Loading

0xmiros commented Oct 22, 2023 •

edited

Loading