I verified the JSDocs style guidelines (in STYLE.md) were followed.

All platform-specific files are named for the platform the code supports as outlined in the README.

All non-platform specific files are named after what they export and are not named 'index.js'. I verified proper file naming conventions were followed for any new files or renamed files.I verified any copy / text that was added to the app is correct English and 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 all numbers, amounts, dates and phone numbers shown in the product are using the localization methods.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.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 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 that comments were added to code that is not self explanatory.

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.

I followed proper code patterns (see Reviewing the code).

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 ran the tests on all platforms & verified they passed on:.

I included screenshots or videos for tests on all platforms.

long loading states that impact usability).

I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g.

verify the default avatar icon is displayed if app is offline)

I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e.

verify an input displays the correct error message if the entered data is not correct)

I added steps to cover failure scenarios (i.e.

I added steps for Staging and/or Production testing in the QA steps section.

I added steps for the expected offline behavior in the Offline steps section.

I added steps for local testing in the Tests section.

I wrote clear testing steps that cover the changes made in this PR.

I linked the correct issue in the # Fixed Issues section above.

Verify that no errors appear in the JS console.

remove flexShrink from workspace name (badge).

Update slack on mac