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: tweak the anonymous footer component design #20884

Merged
merged 14 commits into from
Jul 5, 2023

Conversation

allroundexperts
Copy link
Contributor

@allroundexperts allroundexperts commented Jun 16, 2023

Details

This PR changes the design of the AnonymouseFooter component such that it matches the specs defined here.

Fixed Issues

$ #20699
PROPOSAL: #20699 (comment)

Tests

  1. Open the app and logout if logged in.
  2. Open any public chat room (like ECX announce)
  3. Verify that the footer of the chat is appearing as defined here.
  • Verify that no errors appear in the JS console

Offline tests

N/A

QA Steps

  1. Open the app and logout if logged in.
  2. Open any public chat room (like ECX announce)
  3. Verify that the footer of the chat is appearing as defined here.
  • 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 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 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 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 Screenshot 2023-06-20 at 4 26 30 AM
Mobile Web - Chrome Screenshot 2023-06-16 at 4 17 29 AM
Mobile Web - Safari Screenshot 2023-06-16 at 4 17 39 AM
Desktop Screenshot 2023-06-20 at 4 32 32 AM
iOS Screenshot 2023-06-16 at 4 57 38 AM
Android Screenshot 2023-06-16 at 5 31 26 AM

@allroundexperts allroundexperts requested a review from a team as a code owner June 16, 2023 00:33
@melvin-bot melvin-bot bot requested review from aimane-chnaif and removed request for a team June 16, 2023 00:33
@melvin-bot
Copy link

melvin-bot bot commented Jun 16, 2023

@aimane-chnaif 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]

Copy link
Contributor

@aimane-chnaif aimane-chnaif left a comment

Choose a reason for hiding this comment

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

"Sign in" button is cut or hidden when room name is too long

Screen.Recording.2023-06-16.at.1.26.29.PM.mov

return (
<View style={styles.anonymousRoomFooter}>
<View
onLayout={onLayout}
Copy link
Contributor

Choose a reason for hiding this comment

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

Why changed withWindowDimensions to onLayout? This callback seems slower.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This is needed because we need to change the layout of this component based on the component width rather than the screen size.

Copy link
Contributor

Choose a reason for hiding this comment

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

I think we can calculate width enough from windowWidth. LHN width is fixed as 375.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

We can, but the component won't be fully responsive. Like it will fail inside storybook where there is no left side bar.

Copy link
Contributor

Choose a reason for hiding this comment

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

My concern is when resize window, layout flickers as you see my video.
I think storybook is less important than that.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@marcochavezf Can you share your thoughts here?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Copy link
Contributor

Choose a reason for hiding this comment

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

Oh this is an interesting issue, yeah my initial thought was that the flickering was almost unnoticeable in the video and I agree that an end-user resizing the window would be a rare case. But after seeing the video that @aimane-chnaif posted here, I think the problem is more noticeable when the room is loading on a small screen. It seems that we're not loading the sign-in button for a moment, not sure if it's related to the resizing logic, but agree with @aimane-chnaif we should fix that (at least the sign-in button which causes the report footer to be displayed incorrectly for a moment).

Copy link
Contributor

Choose a reason for hiding this comment

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

This is clearly noticeable when app becomes heavy (i.e. HT account, old device). View onLayout is called a few seconds after mount.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@aimane-chnaif Removed onLayout. Please check.

<View style={[props.isSmallScreenWidth ? styles.alignItemsStart : styles.alignItemsEnd]}>
<View style={styles.anonymousRoomFooterWordmarkAndLogoContainer(isSmallSizeLayout)}>
<View style={[styles.mr4, styles.flexShrink1]}>
<View style={[isSmallSizeLayout ? styles.alignItemsStart : styles.alignItemsEnd]}>
<ExpensifyWordmark style={styles.anonymousRoomFooterLogo} />
</View>
<Text style={[styles.textNormal, styles.textWhite]}>{props.translate('anonymousReportFooter.logoTagline')}</Text>
Copy link
Contributor

Choose a reason for hiding this comment

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

No font family is added here. #20494 (comment)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Handled.

@allroundexperts
Copy link
Contributor Author

allroundexperts commented Jun 16, 2023

"Sign in" button is cut or hidden when room name is too long

Screen.Recording.2023-06-16.at.1.26.29.PM.mov

@aimane-chnaif This was meant to be handled here. No?

@aimane-chnaif
Copy link
Contributor

aimane-chnaif commented Jun 16, 2023

"Sign in" button is cut or hidden when room name is too long
Screen.Recording.2023-06-16.at.1.26.29.PM.mov

@aimane-chnaif This was meant to be handled here. No?

you mean loooong room name case is out of scope for this PR?
If solution for that fix doesn't conflict or revert some of this PR, that's fine.

@allroundexperts
Copy link
Contributor Author

"Sign in" button is cut or hidden when room name is too long
Screen.Recording.2023-06-16.at.1.26.29.PM.mov

@aimane-chnaif This was meant to be handled here. No?

you mean loooong room name case is out of scope for this PR? If solution for that fix doesn't conflict or revert some of this PR, that's fine.

That is my understanding. Correct me if I'm wrong @marcochavezf.

@aimane-chnaif
Copy link
Contributor

I think the main purpose of this PR is to fix wrong designs different from design doc.

  • logo position
  • Sign in button position
  • text styles (color, font, size)

@marcochavezf
Copy link
Contributor

Yes, @aimane-chnaif is right. Only the long name is out of scope here since it would be fixed in the other issue. We're aiming to fix all the style inconsistencies here 🙇🏽‍♂️

@shawnborton
Copy link
Contributor

"Join in on the discussion" still doesn't feel like it's the right font - can you double check that? An easy way to tell is to use a lowercase "g" and see if it is double story or not.

Then for the background color, it looks incorrect as well - it should be the same background color as a preview card or the LHN or an IOU for example.

@allroundexperts
Copy link
Contributor Author

allroundexperts commented Jun 19, 2023

Screenshot 2023-06-20 at 4 32 52 AM

@shawnborton I'm using fontFamily.EXP_NEUE font family. Should it be something else?

I've updated the background colour FYI.

@shawnborton
Copy link
Contributor

That's the right font, but it doesn't look like it's working. Can you add a lowercase g to the sentence so I can check?

@allroundexperts
Copy link
Contributor Author

@shawnborton Here's how it looks.

Screenshot 2023-06-20 at 6 06 37 PM

@shawnborton
Copy link
Contributor

Okay great, thanks for confirming! That looks good to me.

@aimane-chnaif
Copy link
Contributor

Still waiting for @marcochavezf's thoughts on this thread.

This is my concern:

Screen.Recording.2023-06-23.at.1.59.57.PM.mov

@aimane-chnaif
Copy link
Contributor

@allroundexperts please pull main

const hideComposer = isArchivedRoom || !_.isEmpty(props.errors) || !isAllowedToComment;

const isSmallSizeLayout = props.windowWidth - (props.isSmallScreenWidth ? 0 : 375) < variables.anonymousReportFooterBreakpoint;
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
const isSmallSizeLayout = props.windowWidth - (props.isSmallScreenWidth ? 0 : 375) < variables.anonymousReportFooterBreakpoint;
const isSmallSizeLayout = props.windowWidth - (props.isSmallScreenWidth ? 0 : variables.sideBarWidth) < variables.anonymousReportFooterBreakpoint;

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Fixed.

flexDirection: 'row',
alignItems: 'center',
...(isSmallSizeLayout && {
// flex: 1,
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
// flex: 1,

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Fixed.

<View style={styles.mr4}>
<View style={[props.isSmallScreenWidth ? styles.alignItemsStart : styles.alignItemsEnd]}>
<View style={styles.anonymousRoomFooterWordmarkAndLogoContainer(props.isSmallSizeLayout)}>
<View style={[styles.mr4, styles.flexShrink1]}>
Copy link
Contributor

@aimane-chnaif aimane-chnaif Jun 25, 2023

Choose a reason for hiding this comment

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

Suggested change
<View style={[styles.mr4, styles.flexShrink1]}>
<View style={[props.isSmallSizeLayout ? styles.mr1 : styles.mr4, styles.flexShrink1]}>

Copy link
Contributor

Choose a reason for hiding this comment

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

I request this change because 4px is enough for space.

Before fix: (no need to wrap)

Screenshot 2023-06-25 at 7 24 38 PM

After fix:

Screenshot 2023-06-25 at 7 24 29 PM

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Fixed.

@aimane-chnaif
Copy link
Contributor

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
web.mov
Mobile Web - Chrome mchrome
Mobile Web - Safari

msafari

Desktop desktop
iOS

ios

Android android

aimane-chnaif

This comment was marked as outdated.

@melvin-bot melvin-bot bot requested a review from marcochavezf June 25, 2023 19:20
@aimane-chnaif
Copy link
Contributor

Sorry I found issue while testing edge cases. It doesn't make sense to show anonymous footer in archived room. (already hiding on main though was not intentional)
archived

Also, I found bug on main that offline indicator not showing when offline. We can fix that as well here.

So we can update conditions like this:

    const isAnonymousUser = Session.isAnonymousUser();
-   const hideComposer = isArchivedRoom || !_.isEmpty(props.errors) || !isAllowedToComment;
+   const hideComposer = isArchivedRoom || !_.isEmpty(props.errors) || !isAllowedToComment || isAnonymousUser;

    const isSmallSizeLayout = props.windowWidth - (props.isSmallScreenWidth ? 0 : variables.sideBarWidth) < variables.anonymousReportFooterBreakpoint;

    return (
        <>
-           {(isArchivedRoom || hideComposer || isAnonymousUser) && (
+           {hideComposer && (
                <View style={[styles.chatFooter, props.isSmallScreenWidth ? styles.mb5 : null]}>
-                   {isAnonymousUser && (
+                   {isAnonymousUser && !isArchivedRoom && (
                        <AnonymousReportFooter
                            report={props.report}
                            isSmallSizeLayout={isSmallSizeLayout}
                        />
                    )}
                    {isArchivedRoom && <ArchivedReportFooter report={props.report} />}
                    {!props.isSmallScreenWidth && (
                        <View style={styles.offlineIndicatorRow}>{hideComposer && <OfflineIndicator containerStyles={[styles.chatItemComposeSecondaryRow]} />}</View>
                    )}
                </View>
            )}
-           {!hideComposer && (props.shouldShowComposeInput || !props.isSmallScreenWidth) && !isAnonymousUser && (
+           {!hideComposer && (props.shouldShowComposeInput || !props.isSmallScreenWidth) && (
                <View style={[chatFooterStyles, props.isComposerFullSize && styles.chatFooterFullCompose]}>

@allroundexperts
Copy link
Contributor Author

isAnonymousUser

Cool, Fixed @aimane-chnaif!

@aimane-chnaif
Copy link
Contributor

aimane-chnaif commented Jun 25, 2023

@allroundexperts please test again all possible cases on latest codebase: normal/archived rooms, web/resized web/native, online/offline

@allroundexperts
Copy link
Contributor Author

allroundexperts commented Jun 25, 2023

Screenshot 2023-06-26 at 1 18 26 AM Screenshot 2023-06-26 at 1 19 29 AM Screenshot 2023-06-26 at 1 20 08 AM Screenshot 2023-06-26 at 1 21 15 AM Screenshot 2023-06-26 at 1 21 36 AM

I've not tested this on native since deep links seem not be working again. Can you confirm this on your end?

@aimane-chnaif
Copy link
Contributor

You can test by updating Session.isAnonymousUser() condition manually. This condition should not affect styles made in this PR.

@allroundexperts
Copy link
Contributor Author

Screenshot 2023-06-26 at 1 37 15 AM Screenshot 2023-06-26 at 1 37 52 AM Screenshot 2023-06-26 at 1 39 26 AM Screenshot 2023-06-26 at 1 39 46 AM

Copy link
Contributor

@aimane-chnaif aimane-chnaif left a comment

Choose a reason for hiding this comment

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

@marcochavezf all yours!

marcochavezf
marcochavezf previously approved these changes Jun 27, 2023
Copy link
Contributor

@marcochavezf marcochavezf left a comment

Choose a reason for hiding this comment

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

LGTM, thanks guys! Also I won't merge it after SNH

@shawnborton
Copy link
Contributor

Could we make the Sign In button just slightly less wide? Maybe take like 12-16px off of it. This way we have better space available for small viewports.

@shawnborton
Copy link
Contributor

Otherwise this feels good to me!

@aimane-chnaif
Copy link
Contributor

Could we make the Sign In button just slightly less wide? Maybe take like 12-16px off of it. This way we have better space available for small viewports.

@allroundexperts ^
and fix conflict

LGTM, thanks guys! Also I won't merge it after SNH

SNH is over?

@allroundexperts
Copy link
Contributor Author

@shawnborton Here is how it looks after removing 15px.

Screenshot 2023-06-30 at 11 51 28 AM Screenshot 2023-06-30 at 11 51 48 AM

@allroundexperts
Copy link
Contributor Author

Bump @shawnborton!

@shawnborton
Copy link
Contributor

Cool, that works for me, thanks!

Copy link
Contributor

@marcochavezf marcochavezf left a comment

Choose a reason for hiding this comment

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

Perfect, thank you guys, the code LGTM!

@marcochavezf marcochavezf merged commit d2de779 into Expensify:main Jul 5, 2023
1 check passed
@OSBotify
Copy link
Contributor

OSBotify commented Jul 5, 2023

✋ 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

OSBotify commented Jul 7, 2023

🚀 Deployed to staging by https://github.com/marcochavezf in version: 1.3.38-0 🚀

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

@OSBotify
Copy link
Contributor

🚀 Deployed to production by https://github.com/francoisl in version: 1.3.38-7 🚀

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.

5 participants