[CP Staging] Fix Apple and Google SSO when login in from public room with mentions in it

[mountiny]

Details

When signing using Apple SSO as anonymous user from public room in web, the app crashed with following stacktrace:

[Error] TypeError: undefined is not an object (evaluating 'e.indexOf')
cutBefore — str.js:360
p — LoginUtils.ts:32
E — LoginUtils.ts:66
m — MentionUserRenderer.js:52
MentionUserRenderer — MentionUserRenderer.js:70:83
br — react-dom.production.min.js:166:139
Ss — react-dom.production.min.js:215:273
fl — react-dom.production.min.js:279:392
Il — react-dom.production.min.js:279:323
hl — react-dom.production.min.js:279:180
Al — react-dom.production.min.js:272:248
Ua — react-dom.production.min.js:127:105
ll — react-dom.production.min.js:273:82
(anonymous function) — Onyx.js:103

The error comes from expensify-common on this line, where the str seems to be undefined, that is passed from the extractEmailDomain here and that is called from the App here.

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/367462
https://expensify.slack.com/archives/C06HN74HKMG/p1707321835134969

Tests

1. Uninstall New Expensify app from your phone
2. Log out of the mWeb instance
3. Go to some public room eg https://new.expensify.com/r/8329440843915699
4. Make sure that room has mentions in it (the linked on has)
5. Sign in
6. Choose Apple ID
7. Verify the app does not crash

• Verify that no errors appear in the JS console

Offline tests

n/A

QA Steps

Same as tests

• 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 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(theme.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 the PR modifies the form input styles:
  • I verified that all the inputs inside a form are aligned with each other.
  • I added Design label so the design team can review the changes.
• 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.

Screenshots/Videos

Screen.Recording.2024-02-07.at.16.40.37.mp4

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

[melvin-bot]

@marcaaron 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]

[Julesssss]

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: mWeb Chrome
  • iOS: Native
  • iOS: mWeb 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(theme.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 the PR modifies the form input styles:
  • I verified that all the inputs inside a form are aligned with each other.
  • I added Design label so the design team can review the changes.
• 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

[Julesssss]

Great work 🙇

[Julesssss]

Ignoring perf tests

[melvin-bot]

@Julesssss looks like this was merged without a test passing. Please add a note explaining why this was done and remove the Emergency label if this is not an emergency.

[Julesssss]

This resolves a fire, so I ignored the performance check

[OSBotify]

✋ 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]

🚀 Cherry-picked to staging by https://github.com/mountiny in version: 1.4.38-1 🚀

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

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

[trjExpensify]

Parent issue here btw: https://github.com/Expensify/Expensify/issues/367462

[OSBotify]

🚀 Cherry-picked to staging by https://github.com/mountiny in version: 1.4.38-1 🚀

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

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

[OSBotify]

🚀 Deployed to production by https://github.com/marcaaron in version: 1.4.38-6 🚀

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

[github-actions]

Based on the pull request description and diff provided, the PR is fixing an issue with Single Sign-On (SSO) using Apple and Google when a user attempts to login from a public room on the web, particularly in scenarios where the room contains mentions. The changes involve handling email domain checks more gracefully to avoid application crashes.

Relevant Test Cases:

1. ID: 2616811
   Title: Login - Use Magic link - Same session & different session
   Justification: This test is relevant as it pertains to login flows which can potentially be impacted by changes related to SSO methods like Google and Apple login from a public room.

2. ID: 2661872
   Title: Submit expense - Distance Expense - Create distance Expense (Offline)
   Justification: Although not directly related to SSO, login issues in offline scenarios could be indicative of broader network handling issues, which could indirectly affect functionalities like submitting expenses when there's a network state change during login.

3. ID: 2661797
   Title: Public #Room - Anon user can view task and claim after login
   Justification: This test case involves user interactions in a public room that occur after login, making it susceptible to issues arising from SSO-based login problems in public rooms.

4. ID: 3073295
   Title: Custom Room is displayed in Search results
   Justification: The changes to the mention handling logic in rooms may affect the search and display of custom rooms, especially regarding how mentions are processed.

5. ID: 3534637
   Title: Navigate to link of deleted message
   Justification: While this is about navigation, the handling of mentions and potential link issues could impact how successful navigation is when logging in from a URL where mentions may be involved.

These test cases cover the login process, handling of mentions, and potential issues affecting user navigation and interactions within public or custom rooms.

[github-actions]

Testrails Regression Checklist

The following test cases must be verified by reviewers:

• [ ] Login - Magic code is sent once after double tapping "Enter" - 63%
• Room - Employee can create threads and react in room that "Admins only" can post - 75%
• Login - AppleID Sign In - 80%
• Public Rooms - Anon user can view real-time actions and conversation history - 78%
• [ ] Secondary login chat redirected to primary login if there's an exiting conversation - 65%
• Public Rooms - Navigate as Anon and Login with Google - 85%
• Room mention - Room mention is triggered in workspace rooms - 77%

[github-actions]

Testrails Regression Checklist

The following test cases must be verified by reviewers:

• Desktop - Login - Magic link, Magic code and 2FA - 72%
• Public Rooms - Navigate as Anon and Login with Google - 68%
• Room - Employee can create threads and react in room that "Admins only" can post - 66%
• Room - Employee can create a task in Room - 64%
• Room - Description is displayed when user joins a room as whisper - 62%
• Public Rooms - Navigating to Public Rooms as anon user - 60%
• Room mention - Actionable whisper to create a room is triggered - 58%

[github-actions]

Testrails Regression Checklist

The following test cases must be verified by reviewers:

• Room - Settings - 42%
• Room - Settings - Notification Settings (Online/Offline) - 40%
• Share Code - Share link opens NewDot app in correct screen - 39%
• Public Rooms - Navigating to Public Rooms as anon user - 37%
• Public Rooms - Anon user can scroll to the top of the conversation - 36%
• Public Rooms - Anon user can view real-time actions and conversation history - 35%
• Rooms - System message threading in #Admin room - 35%

[github-actions]

Testrails Regression Checklist

The following test cases must be verified by reviewers:

• Public Rooms - Anon user can view real-time actions and conversation history - 70%
• Public Rooms - Navigate as Anon and Login with Google - 65%
• Login - AppleID Sign In - 60%
• Login - Google Sign In - 45%
• Public Room - Join public Room via link while logged in - 40%
• Public Rooms - user is not redirected to sign in when copying, downloading or checking chat info - 35%
• Error Tests - Simulate SMS Failure & validation failure - 30%

[github-actions]

Based on the provided pull request context, the PR addresses a bug related to Apple and Google SSO when logging in from a public room with mentions. The issue was causing the app to crash due to a TypeError in the MentionUserRenderer.js file. The fix involves modifying the logic to safely access the login property using lodashGet to prevent undefined errors.

Here are the test cases that are most relevant to this PR:

1. High (95%)

   • Login - AppleID Sign In - This test case directly relates to the Apple SSO functionality, which is a focus of the PR.

2. Medium (85%)

   • Login - Google Sign In - Although the PR specifically mentions Apple SSO, Google SSO is also mentioned, and changes might affect it similarly.
   • Public Rooms - Navigate as Anon and Login with Google - This test case involves logging in from a public room, which is relevant to the context of the PR.

3. Medium (75%)

   • Public Rooms - Anon user can view real-time actions and conversation history - This test case is related to public room interactions, which are part of the PR's context.

4. Low (60%)

   • Public Rooms - Anon user can scroll to the top of the conversation - While related to public rooms, this test case is less likely to be directly affected by the changes in the PR.

These test cases cover the areas of SSO login and public room interactions, which are the primary focus of the PR.

[github-actions]

Testrails Regression Checklist

The following test cases must be verified by reviewers:

• Login - AppleID Sign In - (95%)
• Public Rooms - Navigate as Anon and Login with Google - (78%)
• Public Rooms - Anon user can view real-time actions and conversation history - (70%)
• Login - Google Sign In (45%)
• Public Rooms - Anon user can scroll to the top of the conversation - (30%)

[github-actions]

Testrails Regression Checklist

The following test cases must be verified by reviewers:

• Login - AppleID Sign In - (95%)
• Public Rooms - Navigating to Public Rooms as anon user - (78%)
• Public Rooms - Anon user can view real-time actions and conversation history - (70%)
• Login - Google Sign In (45%)
• Public Rooms - Navigate as Anon and Login with Google - (30%)

[github-actions]

Testrails Regression Checklist

The following test cases must be verified by reviewers:

• Public Rooms - Navigate as Anon and Login with Google - (95%)
• Public Rooms - Anon user can view real-time actions and conversation history - (78%)
• Public Rooms - Anon user can scroll to the top of the conversation - (70%)
• Login - Google Sign In (45%)
• Login - AppleID Sign In - (30%)

[github-actions]

Testrails Regression Checklist

The following test cases must be verified by reviewers:

• Login - AppleID Sign In - (95%)
• Public Rooms - Navigate as Anon and Login with Google - (78%)
• Public Rooms - Anon user can view real-time actions and conversation history - (70%)
• Login - Google Sign In (45%)
• Public Rooms - Anon user can scroll to the top of the conversation - (30%)

[github-actions]

Testrails Regression Checklist

The following test cases must be verified by reviewers:

• Login - AppleID Sign In - (95%)
• Public Rooms - Navigate as Anon and Login with Google - (78%)
• Public Rooms - Anon user can view real-time actions and conversation history - (70%)
• Login - Google Sign In (45%)
• Public Rooms - Anon user can scroll to the top of the conversation - (30%)

[github-actions]

Testrails Regression Checklist

The following test cases must be verified by reviewers:

• Login - AppleID Sign In - (95%)
• Public Rooms - Navigating to Public Rooms as anon user - (78%)
• Public Rooms - Anon user can view real-time actions and conversation history - (70%)
• Login - Google Sign In (45%)
• Public Rooms - Navigate as Anon and Login with Google - (30%)

[github-actions]

Testrails Regression Checklist

The following test cases must be verified by reviewers:

• Login - AppleID Sign In - (95%)
• Login - Google Sign In - (90%)
• Public Rooms - Navigate as Anon and Login with Google - (85%)
• Public Rooms - Anon user can view real-time actions and conversation history - (75%)
• Public Rooms - Anon user can scroll to the top of the conversation - (45%)

[Julesssss]

new

[github-actions]

Testrails Regression Checklist

The following test cases must be verified by reviewers:

• Public Rooms - Navigate as Anon and Login with Google - (95%)
• Public Rooms - Anon user can view real-time actions and conversation history - (78%)
• Public Rooms - Anon user can scroll to the top of the conversation - (70%)
• Public Rooms - user is not redirected to sign in when copying, downloading or checking chat info (45%)
• Public Room - Join public Room via link while logged in - (30%)

[github-actions]

Testrails Regression Checklist

The following test cases must be verified by reviewers:

• Login - AppleID Sign In - (95%)
• Login - Google Sign In - (90%)
• Public Rooms - Navigate as Anon and Login with Google - (78%)
• Public Rooms - Anon user can view real-time actions and conversation history - (70%)
• Public Rooms - Anon user can scroll to the top of the conversation - (45%)

[github-actions]

Testrails Regression Checklist

The following test cases must be verified by reviewers:

• Login - AppleID Sign In - (95%)
• Public Rooms - Navigate as Anon and Login with Google - (78%)
• Public Rooms - Anon user can view real-time actions and conversation history - (70%)
• Login - Google Sign In (45%)
• Public Rooms - Anon user can scroll to the top of the conversation - (30%)

[github-actions]

Testrails Regression Checklist

The following test cases must be verified by reviewers:

• Login - AppleID Sign In - (95%)
• Public Rooms - Navigating to Public Rooms as anon user - (78%)
• Public Rooms - Anon user can view real-time actions and conversation history - (70%)
• Login - Google Sign In - (45%)
• Public Rooms - Anon user can scroll to the top of the conversation - (30%)

[github-actions]

Testrails Regression Checklist

The following test cases must be verified by reviewers:

• Login - AppleID Sign In - (95%)
• Public Rooms - Navigate as Anon and Login with Google - (78%)
• Public Rooms - Anon user can view real-time actions and conversation history - (70%)
• Login - Google Sign In (45%)
• Public Rooms - Anon user can scroll to the top of the conversation - (30%)

[github-actions]

Testrails Regression Checklist

The following test cases must be verified by reviewers:

• Login - AppleID Sign In - (95%)
• Login - Google Sign In - (90%)
• Public Rooms - Navigate as Anon and Login with Google - (85%)
• Public Rooms - Anon user can view real-time actions and conversation history - (75%)
• Public Rooms - Anon user can scroll to the top of the conversation - (45%)

[github-actions]

Testrails Regression Checklist

The following test cases must be verified by reviewers:

• Public Rooms - Navigate as Anon and Login with Google - (95%)
• Public Rooms - user is not redirected to sign in when copying, downloading or checking chat info - (78%)
• Public Rooms - Anon user can view real-time actions and conversation history - (70%)

[github-actions]

Testrails Regression Checklist

The following test cases must be verified by reviewers:

• Login - AppleID Sign In - (95%)
• Public Rooms - Navigating to Public Rooms as anon user - (78%)
• Public Rooms - Anon user can view real-time actions and conversation history - (70%)
• Public Rooms - Anon user can scroll to the top of the conversation - (70%)

[github-actions]

Testrails Regression Checklist

The following test cases must be verified by reviewers:

• Login - AppleID Sign In - (95%)
• Login - Google Sign In - (90%)
• Public Rooms - Anon user can view real-time actions and conversation history - (78%)
• Public Rooms - Navigate as Anon and Login with Google - (70%)

[github-actions]

Testrails Regression Checklist

The following test cases must be verified by reviewers:

• Login - AppleID Sign In - (95%)
• Login - Google Sign In - (90%)
• Public Rooms - Navigate as Anon and Login with Google - (85%)
• Public Rooms - Anon user can view real-time actions and conversation history - (80%)
• Public Rooms - Anon user can scroll to the top of the conversation - (75%)
• Public Rooms - user is not redirected to sign in when copying, downloading or checking chat info - (70%)

[github-actions]

Testrails Regression Checklist

The following test cases must be verified by reviewers:

• Login - AppleID Sign In - (95%)
• Public Rooms - Navigating to Public Rooms as anon user - (90%)
• Public Rooms - Anon user can view real-time actions and conversation history - (85%)
• Public Rooms - Anon user can scroll to the top of the conversation - (80%)
• Login - Google Sign In - (75%)
• Public Rooms - Navigate as Anon and Login with Google - (70%)

[github-actions]

Testrails Regression Checklist

The following test cases must be verified by reviewers:

• Login - AppleID Sign In - (95%)
• Public Rooms - Navigating to Public Rooms as anon user - (90%)
• Public Rooms - Anon user can view real-time actions and conversation history - (85%)
• Public Rooms - Anon user can scroll to the top of the conversation - (80%)
• Login - Google Sign In - (75%)
• Public Rooms - Navigate as Anon and Login with Google - (70%)

[github-actions]

Testrails Regression Checklist

The following test cases must be verified by reviewers:

• Login - AppleID Sign In - (95%)
• Login - Google Sign In - (90%)
• Public Rooms - Navigating to Public Rooms as anon user - (85%)
• Public Rooms - Anon user can view real-time actions and conversation history - (80%)
• Public Rooms - Anon user can scroll to the top of the conversation - (75%)
• Public Rooms - Navigate as Anon and Login with Google - (70%)

[github-actions]

Testrails Regression Checklist

The following test cases must be verified by reviewers:

• Public Rooms - Anon user can view real-time actions and conversation history - (95%)
• Public Rooms - Navigate as Anon and Login with Google - (90%)
• Public Rooms - Anon user can scroll to the top of the conversation - (85%)
• Login - Google Sign In - (80%)
• Login - AppleID Sign In - (80%)
• Room mention - Room mention is triggered in workspace rooms - (75%)

[Julesssss]

new

[github-actions]

Testrails Regression Checklist

The following test cases must be verified by reviewers:

• Login - AppleID Sign In - (95%)
• Login - Google Sign In - (90%)
• Public Rooms - Navigating to Public Rooms as anon user - (85%)
• Public Rooms - Anon user can view real-time actions and conversation history - (80%)
• Public Rooms - Anon user can scroll to the top of the conversation - (75%)
• Public Rooms - Navigate as Anon and Login with Google - (70%)