Fix: Android - Category - "Default tax rate" briefly changes back to the default one #54239

wildan-m · 2024-12-17T09:45:32Z

Explanation of Change

Ensure Onyx.update is executed before navigation to prevent UI blinking issues, affecting the category name and rate.

Fixed Issues

$ #50078
PROPOSAL: #50078 (comment)

Tests

Open the app
Create a workspace (Always create a new workspace for each test to ensure that the bug can be consistently reproduced)
Navigate to Workspace settings - More features
Enable Taxes, Rules and Workflows
Navigate to Workspace settings - Categories
Tap on any category
Tap on "Default tax rate"
Select "Tax Rate 1 - 5%"
Tap on "Name"
Add a few characters after the current name and tap on the "Save" button
Verify "Default tax rate" should be the one we have set before without it briefly changes back to initial rate

Verify that no errors appear in the JS console

Offline tests

Same as test

QA Steps

Same as test

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

Kapture.2024-12-17.at.16.36.56.mp4

Android: mWeb Chrome

Kapture.2024-12-17.at.16.38.43.mp4

iOS: Native

Kapture.2024-12-17.at.16.28.12.mp4

iOS: mWeb Safari

Kapture.2024-12-17.at.16.31.11.mp4

MacOS: Chrome / Safari

Kapture.2024-12-17.at.16.24.58.mp4

MacOS: Desktop

Kapture.2024-12-17.at.16.39.52.mp4

…x/50078-fix-old-data-briefly-appeared

melvin-bot · 2024-12-17T09:45:38Z

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

allgandalf · 2024-12-18T06:28:33Z

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

Screen.Recording.2024-12-18.at.1.04.21.PM.mov

Android: mWeb Chrome

Screen.Recording.2024-12-18.at.1.08.24.PM.mov

iOS: Native

Screen.Recording.2024-12-18.at.12.30.23.PM.mov

iOS: mWeb Safari

Screen.Recording.2024-12-18.at.12.31.15.PM.mov

MacOS: Chrome / Safari

Screen.Recording.2024-12-18.at.12.18.54.PM.mov

MacOS: Desktop

Screen.Recording.2024-12-18.at.12.26.14.PM.mov

allgandalf

LGTM and tests well!

OSBotify · 2024-12-18T15:12:51Z

✋ 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-23T20:58:49Z

🚀 Deployed to staging by https://github.com/arosiclair in version: 9.0.78-0 🚀

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

github-actions · 2024-12-23T21:42:45Z

🚀 Deployed to staging by https://github.com/arosiclair in version: 9.0.78-0 🚀

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

github-actions · 2024-12-23T21:50:16Z

🚀 Deployed to staging by https://github.com/arosiclair in version: 9.0.78-0 🚀

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

github-actions · 2024-12-24T00:06:00Z

🚀 Deployed to staging by https://github.com/arosiclair in version: 9.0.78-0 🚀

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

github-actions · 2024-12-24T00:53:39Z

🚀 Deployed to staging by https://github.com/arosiclair in version: 9.0.78-0 🚀

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

github-actions · 2024-12-24T19:43:46Z

🚀 Deployed to staging by https://github.com/arosiclair in version: 9.0.78-0 🚀

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

github-actions · 2024-12-24T20:00:42Z

🚀 Deployed to staging by https://github.com/arosiclair in version: 9.0.78-0 🚀

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

github-actions · 2024-12-26T20:27:57Z

🚀 Deployed to production by https://github.com/jasperhuangg in version: 9.0.78-6 🚀

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

wildan-m added 3 commits November 1, 2024 16:27

Fix old data briefly appeared

b8cc629

Merge branch 'main' of https://github.com/wildan-m/App into wildan/fi…

344e373

…x/50078-fix-old-data-briefly-appeared

Add comment

42bfab2

wildan-m requested a review from a team as a code owner December 17, 2024 09:45

melvin-bot bot requested a review from allgandalf December 17, 2024 09:45

melvin-bot bot removed the request for review from a team December 17, 2024 09:45

wildan-m mentioned this pull request Dec 17, 2024

[HOLD for payment 2025-01-02] [$250] Android - Category - "Default tax rate" briefly changes back to the default one #50078

Closed

6 tasks

allgandalf approved these changes Dec 18, 2024

View reviewed changes

melvin-bot bot requested a review from arosiclair December 18, 2024 07:39

arosiclair approved these changes Dec 18, 2024

View reviewed changes

arosiclair merged commit 0ad4b2b into Expensify:main Dec 18, 2024
17 checks passed

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

Deploy Checklist: New Expensify 2024-12-23 #54476

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Fix: Android - Category - "Default tax rate" briefly changes back to the default one #54239

Fix: Android - Category - "Default tax rate" briefly changes back to the default one #54239

wildan-m commented Dec 17, 2024

melvin-bot bot commented Dec 17, 2024

allgandalf commented Dec 18, 2024 •

edited

Loading

allgandalf left a comment

OSBotify commented Dec 18, 2024

github-actions bot commented Dec 23, 2024

github-actions bot commented Dec 23, 2024

github-actions bot commented Dec 23, 2024

github-actions bot commented Dec 24, 2024

github-actions bot commented Dec 24, 2024

github-actions bot commented Dec 24, 2024

github-actions bot commented Dec 24, 2024

github-actions bot commented Dec 26, 2024

Fix: Android - Category - "Default tax rate" briefly changes back to the default one #54239

Fix: Android - Category - "Default tax rate" briefly changes back to the default one #54239

Conversation

wildan-m commented Dec 17, 2024

Explanation of Change

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

melvin-bot bot commented Dec 17, 2024

allgandalf commented Dec 18, 2024 • edited Loading

Reviewer Checklist

Screenshots/Videos

allgandalf left a comment

Choose a reason for hiding this comment

OSBotify commented Dec 18, 2024

github-actions bot commented Dec 23, 2024

github-actions bot commented Dec 23, 2024

github-actions bot commented Dec 23, 2024

github-actions bot commented Dec 24, 2024

github-actions bot commented Dec 24, 2024

github-actions bot commented Dec 24, 2024

github-actions bot commented Dec 24, 2024

github-actions bot commented Dec 26, 2024

allgandalf commented Dec 18, 2024 •

edited

Loading