Skip to content
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

feature: silently update desktop app #40253

Merged

Conversation

gijoe0295
Copy link
Contributor

@gijoe0295 gijoe0295 commented Apr 15, 2024

Details

Press Update in Update required modal should automatically check and install the latest update in the background.

Fixed Issues

$ #39526
PROPOSAL: #39526 (comment)

Tests

  1. Modify package.json's version to 1.4.57-5 (the minimum required version since the group chat releases)
  2. In build-desktop.sh, omit the --publish always param (to disable Apple's notarization process)
  3. Build with npm run desktop-build
  4. Install the build
  5. Open App
  6. Press Update
  7. Verify a dialog shows Update Available
  8. Press Sounds good
  • Verify that no errors appear in the JS console

Offline tests

NA

QA Steps

Precondition: Desktop app's version is 1.4.57-5 or below.

  1. Open App
  2. Press Update
  3. Verify a dialog shows Update Available
  4. Press Sounds good
  5. Verify after a while, app is restarted
  6. Press New Expensify menu >> About New Expensify
  7. Verify the version is the latest production build
  • 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 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.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 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.
  • 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
Screen.Recording.2024-04-26.at.19.59.01-source.mov
Android: mWeb Chrome
Screen.Recording.2024-04-26.at.19.52.31-source.mov
iOS: Native
Screen.Recording.2024-04-26.at.20.06.22-source.mov
iOS: mWeb Safari
Screen.Recording.2024-04-26.at.19.43.30-source.mov
MacOS: Chrome / Safari
Screen.Recording.2024-04-26.at.19.40.43-source.mov
MacOS: Desktop
Screen.Recording.2024-04-26.at.19.36.55-source.mov

@gijoe0295 gijoe0295 changed the title feature: silently update on desktop feature: silently update desktop app Apr 15, 2024
@gijoe0295 gijoe0295 marked this pull request as ready for review April 17, 2024 01:10
@gijoe0295 gijoe0295 requested a review from a team as a code owner April 17, 2024 01:10
@melvin-bot melvin-bot bot requested review from DylanDylann and removed request for a team April 17, 2024 01:10
Copy link

melvin-bot bot commented Apr 17, 2024

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

@gijoe0295
Copy link
Contributor Author

@Beamanator Can you add Build label here? @DylanDylann Hold up reviewing, let me thoroughly test on the adhoc build first, I'll notify you once it's ready.

@Beamanator
Copy link
Contributor

Added label & kicked off build 👍 - https://github.com/Expensify/App/actions/runs/8717438546

Copy link
Contributor

@gijoe0295
Copy link
Contributor Author

gijoe0295 commented Apr 18, 2024

Adhoc builds do not support auto updater so we need to set up local our own release channel locally as instructed here. I'm having problems with signing certificate with my apple developer account, I already contact them about this. Will notify when it's ready for testing.

@gijoe0295
Copy link
Contributor Author

gijoe0295 commented Apr 21, 2024

Hi @Beamanator, I had problem testing the auto updating feature. The Adhoc build, by all means, couldn't be used for that purpose. I also followed the local test instruction here but struggled with the Apple Developer program enrollment. I already paid for it twice (through app and web) but still couldn't use it for unknown reason. I filed a support ticket to Apple but hasn't been replied. Additionally, I spotted many developers had the same problem but couldn't resolve for months. So it's definitely Apple's issue. Thus I want to quick bump you here to see whether either:

  1. Expensify had Apple Developer credentials open for contributors to test this involved feature; or
  2. Is there any other way I could test this?

Hope to get your support, thanks!

Copy link
Contributor

@Beamanator Beamanator left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall this is looking good, just a few tiny changes requested.

As for testing the actual functionality, you're right this can be pretty hard to test & sorry that has been very difficult for you to get the apple developer credentials...

This is a difficult process so it may be enough to just test:

  1. The local app runs fine (npm run desktop)
  2. The staging build runs fine locally (even without signing the build - npm run desktop-build-staging)
  3. Make sure there's no CORS errors, logging in is fine, performance seems fine, etc

desktop/main.ts Outdated Show resolved Hide resolved
package.json Outdated Show resolved Hide resolved
package-lock.json Outdated Show resolved Hide resolved
gijoe0295 and others added 3 commits April 22, 2024 22:34
Co-authored-by: Alex Beaman <dabeamanator@gmail.com>
@gijoe0295
Copy link
Contributor Author

gijoe0295 commented Apr 22, 2024

cc @DylanDylann on #40253 (review). I verified all the above requirements are met. I think for this case we only need to verify if pressing Update actually triggers the corresponding callback in electron runtime.

Note that we can use console.log in main.ts but the log output will be written in ~/Library/Logs/new.expensify.desktop/main.log.

Also note that in order to build desktop, you need to omit the --publish always option here.

@gijoe0295
Copy link
Contributor Author

gijoe0295 commented Apr 23, 2024

@DylanDylann So sorry for this inconvenience again, Apple finally activated my account so I think I have to do the testing. Please hold up your review, I'll complete it today.

@Beamanator
Copy link
Contributor

Note that we can use console.log in main.ts but the log output will be written in ~/Library/Logs/new.expensify.desktop/main.log.

Also note that in order to build desktop, you need to omit the --publish always option here.

Ooh these are pretty interesting suggestions, would you mind bringing these up in #expensify-open-source so we can hopefully make that script better? I'm honestly not super well versed with that script so it could be great to start a convo in slack so more people can see your suggestions 🙏

@gijoe0295
Copy link
Contributor Author

Ooh these are pretty interesting suggestions

@Beamanator Hmm I do not quite understand your points. The log output is the current behavior already pointed out in desktop/README.md. While the build script omit is just hard-coding to bypass build publishing because that required a very complicated setup.

@DylanDylann
Copy link
Contributor

@gijoe0295 Any update here?

@DylanDylann
Copy link
Contributor

DylanDylann commented Apr 24, 2024

Before I test this solution by using dialog.showMessageBox as @gijoe0295's suggestion. I think we can use this way to test this PR on dev env and leave the rest to the QA team after this PR is deployed

cc @Beamanator

@gijoe0295
Copy link
Contributor Author

gijoe0295 commented Apr 24, 2024

@DylanDylann I am stuck on Apple notarization API call for like 3 hours:

electron-notarize:spawn spawning cmd: xcrun args: [
  'notarytool',
  'submit',
  '/var/folders/vw/p4pxkyc56r7cx6qwnz15240r0000gn/T/electron-notarize-B6qu5k/New Expensify.zip',
  '--apple-id',
  '*********',
  '--password',
  '*********',
  '--team-id',
  '*********',
  '--wait',
  '--output-format',
  'json'
] opts: {} +0ms

Yesterday and today morning, they had an outage for Developer ID Notary Service so I couldn't test it. Now seems like their server is in low availability handling pending requests during the outage. I'll retry tonight and tomorrow and notify you when it's done.

@DylanDylann
Copy link
Contributor

@gijoe0295 I think we should use a tricky way to test this PR on dev ( using dialog.showMessageBox to see log) and leave the rest to the QA team after this PR is deployed

@Beamanator What do you think about this way?

@Beamanator
Copy link
Contributor

@DylanDylann To be honest i don't know how that works, but feel free to try it!!

@gijoe0295
Copy link
Contributor Author

@DylanDylann If that's the case, I think we're good for testing and reviewing. I updated test steps and screenshots accordingly.

desktop/main.ts Outdated
/** Menu Item callback to triggers an update check */
const manuallyCheckForUpdates = (menuItem: MenuItem, browserWindow?: BrowserWindow) => {
/** Menu Item callback to trigger an update check */
const manuallyCheckForUpdates = (menuItem?: MenuItem, browserWindow?: BrowserWindow) => {
// Disable item until the check (and download) is complete
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Move this line to the below code block

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@gijoe0295 Small change, please address it

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated!

@@ -201,7 +210,7 @@ const electronUpdater = (browserWindow: BrowserWindow): PlatformSpecificUpdater
if (checkForUpdatesMenuItem) {
checkForUpdatesMenuItem.visible = false;
}
if (browserWindow.isVisible()) {
if (browserWindow.isVisible() && !isSilentUpdating) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@gijoe0295 I still think that we should show a notification to the user after updating version successfully

cc @Beamanator

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm well this is why we're calling it "silent" updating I guess haha. At this point, if the user already clicked "Update" I'm not sure this would require another notification to the user -> Like on Web, we would just refresh & BAM it's updated, no extra notification 🤔

@DylanDylann
Copy link
Contributor

DylanDylann commented Apr 30, 2024

@Beamanator Testing well

Screen.Recording.2024-04-30.at.22.59.01.mov

I change somethings to test this PR manually

diff --git a/desktop/main.ts b/desktop/main.ts
index be3d8722fa..85506eed3a 100644
--- a/desktop/main.ts
+++ b/desktop/main.ts
@@ -139,10 +139,12 @@ const manuallyCheckForUpdates = (menuItem?: MenuItem, browserWindow?: BrowserWin
     autoUpdater
         .checkForUpdates()
         .catch((error) => {
+            dialog.showMessageBox({message: "error"});
             isSilentUpdating = false;
             return {error};
         })
         .then((result) => {
+            dialog.showMessageBox({message: "successful"});
             const downloadPromise = result && 'downloadPromise' in result ? result.downloadPromise : undefined;
 
             if (!browserWindow) {
@@ -615,6 +617,7 @@ const mainWindow = (): Promise<void> => {
 
                 // Automatically check for and install the latest version in the background
                 ipcMain.on(ELECTRON_EVENTS.SILENT_UPDATE, () => {
+                    dialog.showMessageBox({message: "trigger SLIENT UPDATE event"});
                     if (isSilentUpdating) {
                         return;
                     }
diff --git a/src/App.tsx b/src/App.tsx
index 6316fa80fb..27ebfb08b1 100644
--- a/src/App.tsx
+++ b/src/App.tsx
@@ -54,6 +54,10 @@ const fill = {flex: 1};
 function App({url}: AppProps) {
     useDefaultDragAndDrop();
     OnyxUpdateManager();
+    const ErrorComponent = () => {
:...skipping...
diff --git a/desktop/main.ts b/desktop/main.ts
index be3d8722fa..85506eed3a 100644
--- a/desktop/main.ts
+++ b/desktop/main.ts
@@ -139,10 +139,12 @@ const manuallyCheckForUpdates = (menuItem?: MenuItem, browserWindow?: BrowserWin
     autoUpdater
         .checkForUpdates()
         .catch((error) => {
+            dialog.showMessageBox({message: "error"});
             isSilentUpdating = false;
             return {error};
         })
         .then((result) => {
+            dialog.showMessageBox({message: "successful"});
             const downloadPromise = result && 'downloadPromise' in result ? result.downloadPromise : undefined;
 
             if (!browserWindow) {
@@ -615,6 +617,7 @@ const mainWindow = (): Promise<void> => {
 
                 // Automatically check for and install the latest version in the background
                 ipcMain.on(ELECTRON_EVENTS.SILENT_UPDATE, () => {
+                    dialog.showMessageBox({message: "trigger SLIENT UPDATE event"});
                     if (isSilentUpdating) {
                         return;
                     }
diff --git a/src/App.tsx b/src/App.tsx
index 6316fa80fb..27ebfb08b1 100644
--- a/src/App.tsx
+++ b/src/App.tsx
@@ -54,6 +54,10 @@ const fill = {flex: 1};
 function App({url}: AppProps) {
     useDefaultDragAndDrop();
     OnyxUpdateManager();
+    const ErrorComponent = () => {
+        throw new Error('Error in ErrorComponent');
+        // This will throw an error when the component renders
+      };
     return (
         <InitialURLContextProvider url={url}>
             <GestureHandlerRootView style={fill}>
@@ -88,9 +92,12 @@ function App({url}: AppProps) {
                 >
                     <CustomStatusBarAndBackground />
                     <ErrorBoundary errorMessage="NewExpensify crash caught by error boundary">
-                        <ColorSchemeWrapper>
+                        {/* <ColorSchemeWrapper>
                             <Expensify />
                         </ColorSchemeWrapper>
+                         */}
+
+                         <ErrorComponent />
                     </ErrorBoundary>
                 </ComposeProviders>
             </GestureHandlerRootView>
:...skipping...
diff --git a/desktop/main.ts b/desktop/main.ts
index be3d8722fa..85506eed3a 100644
--- a/desktop/main.ts
+++ b/desktop/main.ts
@@ -139,10 +139,12 @@ const manuallyCheckForUpdates = (menuItem?: MenuItem, browserWindow?: BrowserWin
     autoUpdater
         .checkForUpdates()
         .catch((error) => {
+            dialog.showMessageBox({message: "error"});
             isSilentUpdating = false;
             return {error};
         })
         .then((result) => {
+            dialog.showMessageBox({message: "successful"});
             const downloadPromise = result && 'downloadPromise' in result ? result.downloadPromise : undefined;
 
             if (!browserWindow) {
@@ -615,6 +617,7 @@ const mainWindow = (): Promise<void> => {
 
                 // Automatically check for and install the latest version in the background
                 ipcMain.on(ELECTRON_EVENTS.SILENT_UPDATE, () => {
+                    dialog.showMessageBox({message: "trigger SLIENT UPDATE event"});
                     if (isSilentUpdating) {
                         return;
                     }
diff --git a/src/App.tsx b/src/App.tsx
index 6316fa80fb..27ebfb08b1 100644
--- a/src/App.tsx
+++ b/src/App.tsx
@@ -54,6 +54,10 @@ const fill = {flex: 1};
 function App({url}: AppProps) {
     useDefaultDragAndDrop();
     OnyxUpdateManager();
+    const ErrorComponent = () => {
+        throw new Error('Error in ErrorComponent');
+        // This will throw an error when the component renders
+      };
     return (
         <InitialURLContextProvider url={url}>
             <GestureHandlerRootView style={fill}>
@@ -88,9 +92,12 @@ function App({url}: AppProps) {
                 >
                     <CustomStatusBarAndBackground />
                     <ErrorBoundary errorMessage="NewExpensify crash caught by error boundary">
-                        <ColorSchemeWrapper>
+                        {/* <ColorSchemeWrapper>
                             <Expensify />
                         </ColorSchemeWrapper>
+                         */}
+
+                         <ErrorComponent />
                     </ErrorBoundary>
                 </ComposeProviders>
             </GestureHandlerRootView>
diff --git a/src/components/ErrorBoundary/BaseErrorBoundary.tsx b/src/components/ErrorBoundary/BaseErrorBoundary.tsx
index 75f65a06a2..3a36f91822 100644
--- a/src/components/ErrorBoundary/BaseErrorBoundary.tsx
+++ b/src/components/ErrorBoundary/BaseErrorBoundary.tsx
@@ -24,7 +24,7 @@ function BaseErrorBoundary({logError = () => {}, errorMessage, children}: BaseEr
      return (
         <ErrorBoundary
-            fallback={updateRequired ? <UpdateRequiredView /> : <GenericErrorPage />}
+            fallback={true ? <UpdateRequiredView /> : <GenericErrorPage />}
             onError={catchError}
         >
             {children}
diff --git a/src/libs/actions/AppUpdate/updateApp/index.desktop.ts b/src/libs/actions/AppUpdate/updateApp/index.desktop.ts
index 5c1ecbe057..873577b03a 100644
--- a/src/libs/actions/AppUpdate/updateApp/index.desktop.ts
+++ b/src/libs/actions/AppUpdate/updateApp/index.desktop.ts
@@ -1,5 +1,7 @@
 import ELECTRON_EVENTS from '@desktop/ELECTRON_EVENTS';
 
 export default function updateApp() {
+    console.log("Start Updating")
+    
     window.electron.send(ELECTRON_EVENTS.SILENT_UPDATE);
 }
:

@DylanDylann
Copy link
Contributor

DylanDylann commented Apr 30, 2024

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 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 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 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.
  • 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.

Only need to test on Desktop App

Screenshots/Videos

Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari
MacOS: Desktop
Screen.Recording.2024-04-30.at.22.59.01.mov

@melvin-bot melvin-bot bot requested a review from Beamanator April 30, 2024 16:13
@DylanDylann
Copy link
Contributor

@Beamanator Bump, could you help to take a look at this PR?

Copy link
Contributor

@Beamanator Beamanator left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@Beamanator Beamanator merged commit b0123ca into Expensify:main May 5, 2024
16 checks passed
@OSBotify
Copy link
Contributor

OSBotify commented May 5, 2024

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

@kbecciv
Copy link

kbecciv commented May 8, 2024

@b1tjoy @Beamanator Could someone internally verify this PR? Unfortunately, we don't have anyone with the Desktop app's version 1.4.57-5 or below.

@OSBotify
Copy link
Contributor

OSBotify commented May 9, 2024

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

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants