Implement the React-Native Pusher library for iOS and Android

[VickyStash]

Explanation of Change

Update the Pusher module to use @pusher/pusher-websocket-react-native lib on mobile platforms.

Fixed Issues

$ #56480
PROPOSAL: N/A

Tests

• Verify that no errors appear in the JS console

Chat messages receiving

1. Login as User A on one device
2. Login as User B on another device
3. Chat with each other and verify each user is receiving messages from another one.

Expenses

1. Login as User A - workspace admin - on one device.
2. Login as User B - workspace member - on another device.
3. From User B submit the expense to the workspace. Make sure it starts to display for User A.
4. From User A approve and pay expense. Make sure updates are visible for User B.

Make sure "is typing" indicator is working

1. Login as User A on one device
2. Login as User B on another device
3. Start typing the message to User B from User A, User B should see "is typing" note
4. Start typing the message to User A from User B, User A should see "is typing" note

Room Leaving

1. Login as User A to two devices.
2. On both devices open a room.
3. On Device 1 click room details > Leave Room.
4. The user should leave the room on both devices.

Offline tests

N/A

QA Steps

• Verify that no errors appear in the JS console

Same, as in the Tests section

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 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 used JaimeGPT to get English > Spanish translation. I then posted it 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 either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • 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.ts 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 UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
  • I verified that all the inputs inside a form are aligned with each other.
  • I added Design label and/or tagged @Expensify/design 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.
• I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
• 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

Android: Native

android1.mp4

Android: mWeb Chrome

android_web1.mp4

iOS: Native

ios_pt01.mp4

ios_pt02.mp4

iOS: mWeb Safari

ios_web_pt1.mp4

ios_web_pt2.mp4

MacOS: Chrome / Safari + MacOS: Desktop

web+desktop_pt01.mp4

web+desktop_pt2.mp4

[VickyStash]

Failing Verify HybridApp build / Comment on all PRs that are forks (pull_request) check is a known issue and isn't related to the PR.

[melvin-bot]

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

[fabioh8010]

Just NABs. Great work here 🚀

[fabioh8010]

I saw you changed the import structure so you can do like this Pusher.getPusherSocketID() in other files, please make sure this isn't creating cycle dependencies.

[VickyStash]

Yep, I've updated it to follow project rules of file organization for platform-specific implementations.
I believe we have import/no-cycle eslint rule turned on, so if cycle dependencies were the case the eslint check would fail.

[fabioh8010]

Yep, I've updated it to follow project rules of file organization for platform-specific implementations.

Oh yes you are right, we should do this way 👍

I believe we have import/no-cycle eslint rule turned on, so if cycle dependencies were the case the eslint check would fail.

Unfortunately import/no-cycle is not that reliable to catch cycle dependencies, the best way is to check by yourself by running the Android or iOS app with Metro and checking the logs during startup.

[VickyStash]

I've just checked ios metro logs and there are no cycle warnings related to this PR 👌