Fix WS chat shows default avatar when uploading the avatar while offline by bernhardoj · Pull Request #53618 · Expensify/App

bernhardoj · 2024-12-05T05:14:34Z

Explanation of Change

Fixed Issues

$ #53257
PROPOSAL: #53257 (comment)

Tests

Same as QA Steps

Verify that no errors appear in the JS console

Offline tests

Same as QA Steps

QA Steps

Go offline
Create a workspace
Go to workspace settings > Profile
Change the workspace avatar
Go to workspace chat
Verify the workspace avatar on the LHN and workspace chat shows the custom avatar

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

android.mp4

Android: mWeb Chrome

android.mweb.mp4

iOS: Native

ios.mp4

iOS: mWeb Safari

ios.mweb.mp4

MacOS: Chrome / Safari

web.mp4

MacOS: Desktop

desktop.mp4

melvin-bot · 2024-12-05T05:14:39Z

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

paultsimura · 2024-12-05T10:47:10Z

@bernhardoj this case looks like something that can be covered with a unit test.
Could you please add it following this and https://github.com/Expensify/App/blob/main/tests/README.md?

paultsimura · 2024-12-09T08:06:46Z

@bernhardoj bump 👋

bernhardoj · 2024-12-09T10:12:03Z

Checking

…uploaded-while-offline

bernhardoj · 2024-12-09T10:34:27Z

Updated

paultsimura · 2024-12-09T15:32:18Z

@bernhardoj please run prettier and fix the lint issues.

paultsimura · 2024-12-09T15:51:53Z

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 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.ts 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.
For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

2024-12-09.-.16.46.-.android.mp4

Android: mWeb Chrome

2024-12-09.-.16.46.-.chrome.mp4

iOS: Native

2024-12-09.-.16.46.-.Simulator.Screen.Recording.-.iPhone.15.Pro.-.2024-12-09.at.16.43.47.mp4

iOS: mWeb Safari

2024-12-09.-.16.46.-.Simulator.Screen.Recording.-.iPhone.15.Pro.-.2024-12-09.at.16.41.56.mp4

MacOS: Chrome / Safari

2024-12-09.-.16.46.-.Screen.Recording.2024-12-09.at.16.35.00.mp4

MacOS: Desktop

2024-12-09.-.16.46.-.Screen.Recording.2024-12-09.at.16.36.03.mp4

paultsimura · 2024-12-09T15:52:19Z

tests/unit/ReportUtilsTest.ts

    });

+    describe('getWorkspaceIcon', () => {
+        it('should not used cached icon when avatar is updated', () => {


Suggested change

it('should not used cached icon when avatar is updated', () => {

it('should not use cached icon when avatar is updated', () => {

paultsimura · 2024-12-09T15:52:41Z

tests/unit/ReportUtilsTest.ts

+            const workspace = LHNTestUtils.getFakePolicy('1', 'ws');
+            const workspaceChat = LHNTestUtils.getFakeReport();
+            workspaceChat.policyID = workspace.id;
+


Please run prettier.

bernhardoj · 2024-12-10T02:52:13Z

Fixed

paultsimura

LGTM ✔️

MarioExpensify

The code change was minor but the test was a great addition! Thank you

OSBotify · 2024-12-10T13:41:59Z

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

github-actions · 2024-12-10T23:04:09Z

🚀 Deployed to staging by https://github.com/MarioExpensify in version: 9.0.74-0 🚀

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

github-actions · 2024-12-12T01:34:06Z

🚀 Deployed to production by https://github.com/luacmartins in version: 9.0.74-8 🚀

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

fix ws chat shows default avatar when uploading the avatar while offline

b0ebd44

bernhardoj requested a review from a team as a code owner December 5, 2024 05:14

melvin-bot bot requested review from paultsimura and removed request for a team December 5, 2024 05:14

bernhardoj added 2 commits December 9, 2024 18:32

Merge branch 'main' into fix/53257-ws-chat-shows-default-avatar-when-…

d7cda4a

…uploaded-while-offline

added unit test

2861a7d

paultsimura suggested changes Dec 9, 2024

View reviewed changes

bernhardoj added 2 commits December 10, 2024 10:51

prettier

1e920e7

fix wording

1607e1d

paultsimura approved these changes Dec 10, 2024

View reviewed changes

melvin-bot bot requested a review from MarioExpensify December 10, 2024 08:03

MarioExpensify approved these changes Dec 10, 2024

View reviewed changes

MarioExpensify merged commit 3982ed0 into Expensify:main Dec 10, 2024

github-actions bot mentioned this pull request Dec 10, 2024

Deploy Checklist: New Expensify 2024-12-10 #53889

Closed

52 tasks

melvin-bot bot mentioned this pull request Dec 12, 2024

[HOLD for payment 2024-12-19] [$250] Workspace - Workspace chat shows default avatar when custom avatar is uploaded offline #53257

Closed

8 tasks

paultsimura mentioned this pull request Dec 19, 2024

Fix default WS avatar is shown instead of the custom one #49145

Merged

50 tasks

	it('should not used cached icon when avatar is updated', () => {
	it('should not use cached icon when avatar is updated', () => {

Conversation

bernhardoj commented Dec 5, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Explanation of Change

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

melvin-bot bot commented Dec 5, 2024

Uh oh!

paultsimura commented Dec 5, 2024

Uh oh!

paultsimura commented Dec 9, 2024

Uh oh!

bernhardoj commented Dec 9, 2024

Uh oh!

bernhardoj commented Dec 9, 2024

Uh oh!

paultsimura commented Dec 9, 2024

Uh oh!

paultsimura commented Dec 9, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviewer Checklist

Screenshots/Videos

Uh oh!

paultsimura Dec 9, 2024

Choose a reason for hiding this comment

Uh oh!

paultsimura Dec 9, 2024

Choose a reason for hiding this comment

Uh oh!

bernhardoj commented Dec 10, 2024

Uh oh!

paultsimura left a comment

Choose a reason for hiding this comment

Uh oh!

MarioExpensify left a comment

Choose a reason for hiding this comment

Uh oh!

OSBotify commented Dec 10, 2024

Uh oh!

github-actions bot commented Dec 10, 2024

Uh oh!

github-actions bot commented Dec 12, 2024

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

bernhardoj commented Dec 5, 2024 •

edited

Loading

paultsimura commented Dec 9, 2024 •

edited

Loading