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

Fix open some pages by link display page not found #18967

Merged
merged 11 commits into from
May 22, 2023

Conversation

dukenv0307
Copy link
Contributor

@dukenv0307 dukenv0307 commented May 15, 2023

Details

Fixed Issues

$ #18828
PROPOSAL: #18828 (comment)

Tests

  • The workspace setting page should display loading animation until the page is loaded
  1. Login with any account
  2. Go to Setting > Workspace
  3. Open any workspace
  4. Open General settings and copy the URL
  5. Logout and visit the link that is copied above
  6. Login again with the same account in step 1
  7. Verify that the workspace setting page displays loading animation until the page is loaded
  • The report detail page should display loading animation until the page is loaded
  1. Login with any account
  2. Open any admin room
  3. Click on the header to see detail page
  4. Copy the URL
  5. Logout and visit the link that is copied above
  6. Login again with the same account in step 1
  7. Verify that the report detail page displays loading animation until the page is loaded
  • The report setting page should display loading animation until the page is loaded
  1. Login with any account
  2. Open any admin room
  3. Click on the header to see detail page
  4. Open setting and copy the URL
  5. Logout and visit the link that is copied above
  6. Login again with the same account in step 1
  7. Verify that the report setting page displays loading animation until the page is loaded
  • The report participant page should display loading animation until the page is loaded
  1. Login with any account
  2. Open any group chat
  3. Click on the header to see the participant page
  4. Copy the URL
  5. Logout and visit the link that is copied above
  6. Login again with the same account in step 1
  7. Verify that the report participant page displays loading animation until the page is loaded
  • The workspace initial page should display loading animation until the page is loaded
  1. Login with any account
  2. Open Setting > Workspaces
  3. Open any workspace
  4. Copy the URL
  5. Logout and visit the link that is copied above
  6. Login again with the same account in step 1
  7. Verify that the workspace initial page displays loading animation until the page is loaded
  • The workspace member page should display loading animation until the page is loaded
  1. Login with any account
  2. Open Setting > Workspaces
  3. Open any workspace
  4. Open manage members and copy the URL
  5. Logout and visit the link that is copied above
  6. Login again with the same account in step 1
  7. Verify that the workspace member page displays loading animation until the page is loaded
  • The workspace invite message page should display loading animation until the page is loaded
  1. Login with any account
  2. Open Setting > Workspaces
  3. Open any workspace
  4. Open manage members
  5. Click on invite button to open invite page
  6. Select some users and click on next button to open invite message page
  7. Copy the URL
  8. Logout and visit the link that is copied above
  9. Login again with the same account in step 1
  10. Verify that the workspace invite message page displays loading animation until the page is loaded
  • The workspace invite page should display loading animation until the page is loaded
  1. Login with any account
  2. Open Setting > Workspaces
  3. Open any workspace
  4. Open manage members
  5. Click on invite button to open invite page
  6. Copy the URL
  7. Logout and visit the link that is copied above
  8. Login again with the same account in step 1
  9. Verify that the workspace invite page displays loading animation until the page is loaded
  • Verify that no errors appear in the JS console

Offline tests

Same above

QA Steps

  • The workspace setting page should display loading animation until the page is loaded
  1. Login with any account
  2. Go to Setting > Workspace
  3. Open any workspace
  4. Open General settings and copy the URL
  5. Logout and visit the link that is copied above
  6. Login again with the same account in step 1
  7. Verify that the workspace setting page displays loading animation until the page is loaded
  • The report detail page should display loading animation until the page is loaded
  1. Login with any account
  2. Open any admin room
  3. Click on the header to see detail page
  4. Copy the URL
  5. Logout and visit the link that is copied above
  6. Login again with the same account in step 1
  7. Verify that the report detail page displays loading animation until the page is loaded
  • The report setting page should display loading animation until the page is loaded
  1. Login with any account
  2. Open any admin room
  3. Click on the header to see detail page
  4. Open setting and copy the URL
  5. Logout and visit the link that is copied above
  6. Login again with the same account in step 1
  7. Verify that the report setting page displays loading animation until the page is loaded
  • The report participant page should display loading animation until the page is loaded
  1. Login with any account
  2. Open any group chat
  3. Click on the header to see the participant page
  4. Copy the URL
  5. Logout and visit the link that is copied above
  6. Login again with the same account in step 1
  7. Verify that the report participant page displays loading animation until the page is loaded
  • The workspace initial page should display loading animation until the page is loaded
  1. Login with any account
  2. Open Setting > Workspaces
  3. Open any workspace
  4. Copy the URL
  5. Logout and visit the link that is copied above
  6. Login again with the same account in step 1
  7. Verify that the workspace initial page displays loading animation until the page is loaded
  • The workspace member page should display loading animation until the page is loaded
  1. Login with any account
  2. Open Setting > Workspaces
  3. Open any workspace
  4. Open manage members and copy the URL
  5. Logout and visit the link that is copied above
  6. Login again with the same account in step 1
  7. Verify that the workspace member page displays loading animation until the page is loaded
  • The workspace invite message page should display loading animation until the page is loaded
  1. Login with any account
  2. Open Setting > Workspaces
  3. Open any workspace
  4. Open manage members
  5. Click on invite button to open invite page
  6. Select some users and click on next button to open invite message page
  7. Copy the URL
  8. Logout and visit the link that is copied above
  9. Login again with the same account in step 1
  10. Verify that the workspace invite message page displays loading animation until the page is loaded
  • The workspace invite page should display loading animation until the page is loaded
  1. Login with any account
  2. Open Setting > Workspaces
  3. Open any workspace
  4. Open manage members
  5. Click on invite button to open invite page
  6. Copy the URL
  7. Logout and visit the link that is copied above
  8. Login again with the same account in step 1
  9. Verify that the workspace invite page displays loading animation until the page is loaded
  • 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 / Chrome
    • iOS / native
    • iOS / 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
    • 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 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

Web
  • The workspace setting page should display loading animation until the page is loaded
Screencast.from.16-05-2023.09.55.55.webm
  • The report detail page should display loading animation until the page is loaded
Screencast.from.16-05-2023.09.57.23.webm
  • The report setting page should display loading animation until the page is loaded
Screencast.from.16-05-2023.10.19.48.webm
  • The report participant page should display loading animation until the page is loaded
Screencast.from.16-05-2023.09.59.43.webm
  • The workspace initial page should display loading animation until the page is loaded
Screencast.from.16-05-2023.10.02.24.webm
  • The workspace member page should display loading animation until the page is loaded
Screencast.from.16-05-2023.10.03.44.webm
  • The workspace invite message page should display loading animation until the page is loaded
Screencast.from.16-05-2023.10.04.52.webm
  • The workspace invite page should display loading animation until the page is loaded
Screencast.from.16-05-2023.16.01.38.webm
Mobile Web - Chrome
  • The workspace setting page should display loading animation until the page is loaded
Record_2023-05-16-10-31-33.mp4
  • The report detail page should display loading animation until the page is loaded
Record_2023-05-16-10-35-13.mp4
  • The report setting page should display loading animation until the page is loaded
Record_2023-05-16-10-36-16.mp4
  • The report participant page should display loading animation until the page is loaded
Record_2023-05-16-10-37-20.mp4
  • The workspace initial page should display loading animation until the page is loaded
Record_2023-05-16-10-40-21.mp4
  • The workspace member page should display loading animation until the page is loaded
Record_2023-05-16-10-41-18.mp4
  • The workspace invite message page should display loading animation until the page is loaded
Record_2023-05-16-10-42-36.mp4
  • The workspace invite page should display loading animation until the page is loaded
Record_2023-05-16-16-03-03.mp4
Mobile Web - Safari
  • The workspace setting page should display loading animation until the page is loaded
Screen-Recording-2023-05-16-at-14.43.14-1.mp4
  • The report detail page should display loading animation until the page is loaded
Screen-Recording-2023-05-16-at-14.46.20-1.mp4
  • The report setting page should display loading animation until the page is loaded
Screen-Recording-2023-05-16-at-14.47.33-1.mp4
  • The report participant page should display loading animation until the page is loaded
Screen.Recording.2023-05-16.at.14.49.26-1.mp4
  • The workspace initial page should display loading animation until the page is loaded
Screen.Recording.2023-05-16.at.14.51.59-1.mp4
  • The workspace member page should display loading animation until the page is loaded
Screen.Recording.2023-05-16.at.14.52.56-1.mp4
  • The workspace invite message page should display loading animation until the page is loaded
Screen.Recording.2023-05-16.at.14.54.07-1.mp4
  • The workspace invite page should display loading animation until the page is loaded
Screen.Recording.2023-05-16.at.16.55.40-1.mp4
Desktop

Cannot open with deep link because this bug

iOS

When opening app with a deep link that is different /r/:reportID, the app always opens sidebar screen after login

Android

Same IOS above

Here is example

Screencast.from.16-05-2023.16.11.37.webm

@dukenv0307 dukenv0307 marked this pull request as ready for review May 16, 2023 09:39
@dukenv0307 dukenv0307 requested a review from a team as a code owner May 16, 2023 09:39
@melvin-bot melvin-bot bot requested review from dangrous and mollfpr and removed request for a team May 16, 2023 09:39
@melvin-bot
Copy link

melvin-bot bot commented May 16, 2023

@dangrous @mollfpr One of you needs to 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]

@mollfpr
Copy link
Contributor

mollfpr commented May 17, 2023

if (this.props.isLoadingReportData && _.isEmpty(this.props.iouReport)) {
            return <FullScreenLoadingIndicator />;
        }

@dukenv0307 I think we can create a wrapper component to the above logic.

@dukenv0307
Copy link
Contributor Author

@mollfpr That mean wrapper component is loading component if data is loading and it is page not found component otherwhise. Is that right?

@mollfpr
Copy link
Contributor

mollfpr commented May 17, 2023

    if (props.isLoadingReportData && _.isEmpty(props.policy)) {
        return <FullscreenLoadingIndicator />;
    }

@dukenv0307 Sorry, I mean the above logic for the workspace pages. The not found page can be from the withPolicy.

@dukenv0307
Copy link
Contributor Author

@mollfpr So what shoud we change?

@dukenv0307
Copy link
Contributor Author

@mollfpr So we should move the above logic into withPolicy with workspace pages same as withReportOrNotFound?

@mollfpr
Copy link
Contributor

mollfpr commented May 17, 2023

@dukenv0307 On second thought, I think there are advantages to current changes. So I think we are good now, I'll start the test 👍

@@ -113,6 +118,10 @@ class DetailsPage extends React.PureComponent {
const phoneNumber = getPhoneNumber(details);
const phoneOrEmail = isSMSLogin ? getPhoneNumber(details) : details.login;

if (this.props.isLoadingReportData && _.isEmpty(login)) {
return <FullscreenLoadingIndicator />;
}
Copy link
Contributor

Choose a reason for hiding this comment

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

@dukenv0307 Do we need to add a loading indicator to DetailsPage? I don't see any loading indicator in my test after signing in. The page will display fine; as long the login params are provided another way, it will show not found page.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@mollfpr Yes you right, login is get from params so that _isEmpty(login) is always false if login has in parmas.

if (props.isLoadingReportData && _.isEmpty(props.policy)) {
return <FullscreenLoadingIndicator />;
}

Copy link
Contributor

Choose a reason for hiding this comment

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

Sorry for the back and forth @dukenv0307.

@mollfpr So we should move the above logic into withPolicy with workspace pages same as withReportOrNotFound?

Seems you understand what I mean yesterday, I don't know what the other things I have are.

I just try create a new HOC for accomodate the return of fullscreen loading if the policy is not provided.

export default function (WrappedComponent) {
    const propTypes = {
        isLoadingReportData: PropTypes.bool,
        ...policyPropTypes,
    };

    const defaultProps = {
        isLoadingReportData: true,
        ...policyDefaultProps,
    };

    const WithPolicyAndFullscreenLoading = (props) => {
        if (props.isLoadingReportData && _.isEmpty(props.policy)) {
            return <FullscreenLoadingIndicator />;
        }

        const rest = _.omit(props, ['forwardedRef']);
        return (
            <WrappedComponent
                // eslint-disable-next-line react/jsx-props-no-spreading
                {...rest}
                ref={props.forwardedRef}
            />
        );
    };

    WithPolicyAndFullscreenLoading.propTypes = propTypes;
    WithPolicyAndFullscreenLoading.defaultProps = defaultProps;
    WithPolicyAndFullscreenLoading.displayName = `WithPolicyAndFullscreenLoading(${getComponentDisplayName(WrappedComponent)})`;

    const withPolicyAndFullscreenLoading = React.forwardRef((props, ref) => (
        <WithPolicyAndFullscreenLoading
            // eslint-disable-next-line react/jsx-props-no-spreading
            {...props}
            forwardedRef={ref}
        />
    ));

    return compose(
        withPolicy,
        withOnyx({
            isLoadingReportData: {
                key: ONYXKEYS.IS_LOADING_REPORT_DATA,
            },
        }),
    )(withPolicyAndFullscreenLoading);
}

So we just need to replace withPolicy with withPolicyAndFullscreenLoading in the workspace pages.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@mollfpr Cool, I update right now.

@dukenv0307
Copy link
Contributor Author

dukenv0307 commented May 18, 2023

@mollfpr I just updated new HOC for workspace pages, and restore detail page. And I also tested again workspace pages with new HOC, it works well. Please help to check again if I miss something.
And then should we remove test step for detail page after we restored it?

if (this.props.isLoadingReportData && _.isEmpty(this.props.iouReport)) {
return <FullScreenLoadingIndicator />;
}

Copy link
Contributor

Choose a reason for hiding this comment

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

@dukenv0307 I think we don't need this. When I click on the IOU preview now it's redirecting to the money request report or money request thread report.

@dukenv0307
Copy link
Contributor Author

@mollfpr I just updated code and test steps

@mollfpr
Copy link
Contributor

mollfpr commented May 22, 2023

@dukenv0307 Thanks! Overall it tests well, and the code looks good to me 👍; I'm on my way to completing the recordings.

@mollfpr
Copy link
Contributor

mollfpr commented May 22, 2023

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 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
18967.Web.-.Report.mov
18967.Web.-.Workspace.mov
Mobile Web - Chrome
18967.mWeb.Chrome.-.Workspace.mp4
18967.mWeb.Chrome.-.Report.mp4
Mobile Web - Safari
18967.mWeb.Safari.-.Report.mp4
18967.mWeb.Safari.-.Workspace.mp4
Desktop
18967.Desktop.-.Report.mov
18967.Desktop.-.Workspace.mov
iOS
Android

Copy link
Contributor

@mollfpr mollfpr left a comment

Choose a reason for hiding this comment

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

LGTM and tests well 👍

All yours @dangrous

Copy link
Contributor

@dangrous dangrous left a comment

Choose a reason for hiding this comment

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

Looks great!

@dangrous dangrous merged commit 5296b4e into Expensify:main May 22, 2023
@OSBotify
Copy link
Contributor

✋ 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
Copy link
Contributor

🚀 Deployed to staging by https://github.com/dangrous in version: 1.3.17-0 🚀

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

@OSBotify
Copy link
Contributor

🚀 Deployed to production by https://github.com/chiragsalian in version: 1.3.17-5 🚀

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
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants