Feat/xero import customer by hungvu193 · Pull Request #41377 · Expensify/App

hungvu193 · 2024-05-01T04:15:56Z

Details

Fixed Issues

$ #39733
PROPOSAL: N/A

Tests

Precondition: User must connect to Xero

Go to workspace => Accounting (Enable Accounting in MoreFeature page incase you don't have Accounting permission).
Choose Import => Re-bill customers
Toggle Import switch
Verify it works as expected.

Verify that no errors appear in the JS console

Offline tests

Same as Tests.

QA Steps

Same as Tests.

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

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

hungvu193 · 2024-05-01T08:22:39Z

Hold for #40984

melvin-bot · 2024-05-01T12:15:28Z

@rayane-djouah 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]

…omer

rushatgabhane · 2024-05-01T12:39:56Z

    importCustomers: boolean;
    importTaxRates: boolean;
    importTrackingCategories: boolean;
+    syncCustomers: IntegrationEntityMap;


Please remove syncCustomers and use importCustomers.
The docs isn't accurate. The correct key is importCustomers, and we'll have to update it everywhere

I'm getting errors from server, so I can't send the API request, but the server response syncCustomers.

ohh interesting, my bad then 😅

I see the issue now, let me fix it

if I updated it to importCustomers API still throw errors so I'm asking for help.

that's BE issue so I don't think it's related, bump @lakchote for helping here

Here's the request:

curl 'https://dev.new.expensify.com:8082/api/UpdatePolicyConnectionConfiguration?' \ -H 'Accept: */*' \ -H 'Accept-Language: en-US,en;q=0.9' \ -H 'Connection: keep-alive' \ -H 'Content-Type: multipart/form-data; boundary=----WebKitFormBoundarygHxrwBguyZCnbbdZ' \ -H 'Cookie: initialReferer=https%3A%2F%2Fdev.new.expensify.com%3A8082%2F; browserGUID=657b1e1ccf98b; mutiny.user.token=88dfd70a-3aa5-4ad9-9080-4f54dbfb73ef; _gcl_au=1.1.1489038878.1709459015; _ga=GA1.1.188411470.1709459015; cf_clearance=M1DirP9FL5i8zejTc7rb_GLuOKdGsyp3cgg9jOJI7rU-1714555619-1.0.1.1-F.I358ic4k57LOYGQU6UmFW1pLakSPDCfFqWltRyb0CZ0yyFgbgxdsmlwThvn4glOQr1Tld4QC0AGAoFQost4Q; _clck=8v84vb%7C2%7Cfle%7C0%7C1523; _uetsid=f5a8bd70079c11efb4b61be823255bec; _uetvid=80f5ea40d94211eea783efc64819d0ae; _clsk=1jc628l%7C1714557292125%7C3%7C1%7Ct.clarity.ms%2Fcollect; _ga_6BR2QJRCCD=GS1.1.1714555619.10.1.1714557292.60.0.0; _cfuvid=onvcaqxpOn013xLmz_Y_h0WpFucfhvDpjK4TEC1k75s-1714568731274-0.0.1.1-604800000; __cf_bm=58TeQrCPXirZSdhJBZkR1rHYuF89iKk9FZrMPLwQzcE-1714572465-1.0.1.1-RcyXwMqSPocs9YpED92uIGK8EObzH5o0fev3LWMVPuxVDR_aR.B4vvdo7_5VMQwZBkZybZ3AOy4.akQlxwlG5Q' \ -H 'Origin: https://dev.new.expensify.com:8082' \ -H 'Referer: https://dev.new.expensify.com:8082/settings/workspaces/67D374BFA1B0F027/accounting/xero/import' \ -H 'Sec-Fetch-Dest: empty' \ -H 'Sec-Fetch-Mode: cors' \ -H 'Sec-Fetch-Site: same-origin' \ -H 'User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36' \ -H 'sec-ch-ua: "Chromium";v="124", "Google Chrome";v="124", "Not-A.Brand";v="99"' \ -H 'sec-ch-ua-mobile: ?0' \ -H 'sec-ch-ua-platform: "macOS"' \ --data-raw $'------WebKitFormBoundarygHxrwBguyZCnbbdZ\r\nContent-Disposition: form-data; name="policyID"\r\n\r\n67D374BFA1B0F027\r\n------WebKitFormBoundarygHxrwBguyZCnbbdZ\r\nContent-Disposition: form-data; name="connectionName"\r\n\r\nxero\r\n------WebKitFormBoundarygHxrwBguyZCnbbdZ\r\nContent-Disposition: form-data; name="settingName"\r\n\r\nimportCustomers\r\n------WebKitFormBoundarygHxrwBguyZCnbbdZ\r\nContent-Disposition: form-data; name="settingValue"\r\n\r\nfalse\r\n------WebKitFormBoundarygHxrwBguyZCnbbdZ\r\nContent-Disposition: form-data; name="idempotencyKey"\r\n\r\nimportCustomers\r\n------WebKitFormBoundarygHxrwBguyZCnbbdZ\r\nContent-Disposition: form-data; name="appversion"\r\n\r\n1.4.69-0\r\n------WebKitFormBoundarygHxrwBguyZCnbbdZ\r\nContent-Disposition: form-data; name="apiRequestType"\r\n\r\nwrite\r\n------WebKitFormBoundarygHxrwBguyZCnbbdZ\r\nContent-Disposition: form-data; name="pusherSocketID"\r\n\r\n708991.54308\r\n------WebKitFormBoundarygHxrwBguyZCnbbdZ\r\nContent-Disposition: form-data; name="shouldRetry"\r\n\r\ntrue\r\n------WebKitFormBoundarygHxrwBguyZCnbbdZ\r\nContent-Disposition: form-data; name="canCancel"\r\n\r\ntrue\r\n------WebKitFormBoundarygHxrwBguyZCnbbdZ\r\nContent-Disposition: form-data; name="authToken"\r\n\r\nAE80628CBA1BD23729B5986BDC63B98B807C33BF8C268A74CA95847D3ABA55BF75DE93D7C9A5ADC8D72676FDC130C1F765717BEBEBFF894EBEE5CD15BA2EBB8C7CDE486549F1E2CFE99361A57973938EEDF74E4F26996768CA32109FB28DE4D51B9DD33FEDCC5A804ECF658DC9B4718CDD1893766D3DBE718971ECC10B6973CFEBC8FDBA80FE1EC9A1A2871DD6FF5DBDAC33DA2A899E17EE74701773482BCC36CEFCA335FFB1A6976D4187FA7CCF87388B642F8DBAEDBD3C4ACA09686CFF24FDE6C8B2B96167B37A179456265E63985865176CE461AC6CBF6FF000C295AF538DF6947F5D2B401A14BCCB6D7790293919197F9DC445260B9CA84658AC0A9CD932D41DA070BA547BA4294E5184E18FFC05E7F386D025AC26D89AB449A0591A2036FA01131D6E9A05804DF210192B7B39AED0EA35B960CCB3B2BEFAD8C2B0FB769CDDF4936D7174D8354E5071EBE77E4029A06ACEC187A5FBFCD155CB6CFE990AB2\r\n------WebKitFormBoundarygHxrwBguyZCnbbdZ\r\nContent-Disposition: form-data; name="referer"\r\n\r\necash\r\n------WebKitFormBoundarygHxrwBguyZCnbbdZ\r\nContent-Disposition: form-data; name="platform"\r\n\r\nweb\r\n------WebKitFormBoundarygHxrwBguyZCnbbdZ\r\nContent-Disposition: form-data; name="api_setCookie"\r\n\r\nfalse\r\n------WebKitFormBoundarygHxrwBguyZCnbbdZ\r\nContent-Disposition: form-data; name="email"\r\n\r\nhungvv193@gmail.com\r\n------WebKitFormBoundarygHxrwBguyZCnbbdZ\r\nContent-Disposition: form-data; name="isFromDevEnv"\r\n\r\ntrue\r\n------WebKitFormBoundarygHxrwBguyZCnbbdZ--\r\n'

It's a backend issue. The correct key (importCustomers) needs be added as a valid connection key.

Thanks @lakchote , Should we hold this PR for BE changes?

PR to fix that is up here (internal engineers).

hungvu193 · 2024-05-01T12:53:47Z

@rushatgabhane Here's the docs I mentioned
https://docs.google.com/document/d/1VEIzxwNzedLNestAFVT5InGvD4N6FHb0922xjMGOkko/edit#heading=h.fj7tiagvbajy

hungvu193 · 2024-05-01T13:07:35Z

@lakchote I'm getting this error when trying to UpdatePolicyConnect, it was working fine few hours ago 🤦

Co-authored-by: Rushat Gabhane <rushatgabhane@gmail.com>

rushatgabhane

App crash on navigating to accounting page -

hungvu193 · 2024-05-01T14:11:20Z

App crash on navigating to accounting page -

I think it has the same root cause: #41411

hungvu193 · 2024-05-01T14:14:07Z

Feels like lint is broken 😮‍💨

rushatgabhane · 2024-05-01T14:28:06Z

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.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

Screen.Recording.2024-05-02.at.14.07.28.mov

MacOS: Desktop

rushatgabhane · 2024-05-01T14:32:19Z

@hungvu193 i think it's working now. Can you please retest

hungvu193 · 2024-05-01T14:35:17Z

@hungvu193 i think it's working now. Can you please retest

Still doesn't work on my end :(

lakchote · 2024-05-02T03:54:50Z

@hungvu193 it should work now:

hungvu193 · 2024-05-02T03:56:37Z

Awesome, I'll verify it after my lunch.
@rushatgabhane can you complete the checklist in the meantime?

hungvu193 · 2024-05-02T06:36:11Z

It's working now! All yours @rushatgabhane

Screen.Recording.2024-05-02.at.13.35.40.mov

rushatgabhane

LGTM @lakchote

OSBotify · 2024-05-02T09:07:29Z

✋ 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 · 2024-05-07T01:38:10Z

🚀 Deployed to production by https://github.com/marcaaron in version: 1.4.70-5 🚀

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

hungvu193 force-pushed the feat/xero-import-customer branch from 8701d96 to ccdc9d2 Compare May 1, 2024 04:16

xero import customer

b6e964d

hungvu193 force-pushed the feat/xero-import-customer branch from ccdc9d2 to b6e964d Compare May 1, 2024 04:32

hungvu193 added 2 commits May 1, 2024 13:42

add connection layout

3f7639f

fix linting

5b7c037

hungvu193 mentioned this pull request May 1, 2024

[$250] [Awaiting Payment 14th May] [Wave Collect] [Xero] [Import Flow] Create the Customers page #39733

Closed

add pending field for switch

f021eff

fix linting

5fc3442

hungvu193 marked this pull request as ready for review May 1, 2024 12:15

hungvu193 requested a review from a team as a code owner May 1, 2024 12:15

melvin-bot Bot removed the request for review from a team May 1, 2024 12:15

melvin-bot Bot requested a review from rayane-d May 1, 2024 12:15

Merge remote-tracking branch 'origin/main' into feat/xero-import-cust…

f9eb8c5

…omer

rushatgabhane reviewed May 1, 2024

View reviewed changes

resolve conflicts

e8f04da

rushatgabhane reviewed May 1, 2024

View reviewed changes

Comment thread src/pages/workspace/accounting/xero/XeroImportPage.tsx

update to use importCustomers

b459314

hungvu193 force-pushed the feat/xero-import-customer branch from 5793617 to b459314 Compare May 1, 2024 14:03

rushatgabhane reviewed May 1, 2024

View reviewed changes

Comment thread src/pages/workspace/accounting/PolicyAccountingPage.tsx Outdated

remove unused spacing

a937e6e

Co-authored-by: Rushat Gabhane <rushatgabhane@gmail.com>

rushatgabhane suggested changes May 1, 2024

View reviewed changes

hungvu193 commented May 1, 2024

View reviewed changes

Comment thread src/pages/workspace/accounting/PolicyAccountingPage.tsx Outdated

Update src/pages/workspace/accounting/PolicyAccountingPage.tsx

bad19d0

lakchote approved these changes May 2, 2024

View reviewed changes

rushatgabhane approved these changes May 2, 2024

View reviewed changes

lakchote merged commit 20bd114 into Expensify:main May 2, 2024

github-actions Bot mentioned this pull request May 2, 2024

Deploy Checklist: New Expensify 2024-05-02 #41494

Closed

60 tasks

lakchote mentioned this pull request May 3, 2024

[Awaiting payment May 14th] [Wave Collect] [Xero] [Import Flow] Create the ConnectionLayoutComponent #39730

Closed

Uh oh!

Conversation

hungvu193 commented May 1, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Details

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

hungvu193 commented May 1, 2024

Uh oh!

melvin-bot Bot commented May 1, 2024

Uh oh!

rushatgabhane May 1, 2024

Choose a reason for hiding this comment

Uh oh!

hungvu193 May 1, 2024

Choose a reason for hiding this comment

Uh oh!

rushatgabhane May 1, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

hungvu193 May 1, 2024

Choose a reason for hiding this comment

Uh oh!

hungvu193 May 1, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

hungvu193 May 1, 2024

Choose a reason for hiding this comment

Uh oh!

hungvu193 May 1, 2024

Choose a reason for hiding this comment

Uh oh!

lakchote May 1, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

hungvu193 May 1, 2024

Choose a reason for hiding this comment

Uh oh!

lakchote May 1, 2024

Choose a reason for hiding this comment

Uh oh!

hungvu193 commented May 1, 2024

Uh oh!

hungvu193 commented May 1, 2024

Uh oh!

Uh oh!

Uh oh!

rushatgabhane left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

hungvu193 commented May 1, 2024

Uh oh!

hungvu193 commented May 1, 2024

Uh oh!

Uh oh!

rushatgabhane commented May 1, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviewer Checklist

Screenshots/Videos

Uh oh!

rushatgabhane commented May 1, 2024

Uh oh!

hungvu193 commented May 1, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

lakchote commented May 2, 2024

Uh oh!

hungvu193 commented May 2, 2024

Uh oh!

hungvu193 commented May 2, 2024

Uh oh!

hungvu193 commented May 1, 2024 •

edited

Loading

rushatgabhane May 1, 2024 •

edited

Loading

hungvu193 May 1, 2024 •

edited

Loading

lakchote May 1, 2024 •

edited

Loading

rushatgabhane left a comment •

edited

Loading

rushatgabhane commented May 1, 2024 •

edited

Loading

hungvu193 commented May 1, 2024 •

edited

Loading