-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[$250] QBD - Auto-sync toggle does not work correctly #52132
Comments
Triggered auto assignment to @johncschuster ( |
Job added to Upwork: https://www.upwork.com/jobs/~021856102760605829790 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @suneox ( |
Triaged |
Hi, I'm Nicolay from Callstack - expert contributor group - and I would like to work on this issue. |
@johncschuster, @suneox Whoops! This issue is 2 days overdue. Let's get this updated quick! |
I was able to reproduce / the issue happens on QBO as well. I will take over the issue from @suneox as C+ reviewer, coming from this Slack thread. Let's go with @narefyev91 from expert contributor group as they've shown interest in fixing the issue! 🎀👀🎀 C+ reviewed |
Triggered auto assignment to @aldo-expensify, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
Have we confirmed this a frontend issue? |
📣 @suneox 🎉 An offer has been automatically sent to your Upwork account for the Reviewer role 🎉 Thanks for contributing to the Expensify app! |
@aldo-expensify Looked into it and here's what happens: When we turn Auto-sync off JSON{
"jsonCode": 200,
"requestID": "8e31e2695c68cf1b-SJC",
"onyxData": [
{
"key": "policy_E12DF2A9245F1530",
"onyxMethod": "merge",
"value": {
"connections": {
"quickbooksDesktop": {
"config": {
"autoSync": {
"enabled": false,
"jobID": null
}
}
}
}
}
}
],
"previousUpdateID": 2960739932,
"lastUpdateID": 2960747654
} After QBD / QBO syncs, FE calls JSON{
"onyxData": [
{
"key": "policy_E12DF2A9245F1530",
"onyxMethod": "merge",
"value": {
"connections": {
"quickbooksDesktop": {
"config": {
"autoSync": {
"enabled": true
}
}
}
}
}
},
{
"key": "policy_E12DF2A9245F1530",
"onyxMethod": "merge",
"value": {
"connections": {
"quickbooksDesktop": {
"config": {
"autoSync": {
"jobID": "9086846025541357"
}
}
}
}
}
},
{
"key": "userMetadata",
"onyxMethod": "set",
"value": {
"accountID": 15752938,
"email": "[email protected]",
"freeTrial": false,
"planType": "corporate",
"role": "admin",
"tryNewDotDismissed": false
}
}
],
"lastUpdateID": "2960783676",
"previousUpdateID": "2960782355",
"jsonCode": 200,
"requestID": "8e31e7992b2f2536-SJC"
} Looks like the first API call does not seem to persist the autoSync on the BE side which might have something to do with the fact that ♻️ More contextApp/src/libs/actions/connections/QuickbooksDesktop.ts Lines 522 to 531 in 992e5d4
When we call the function in: App/src/pages/workspace/accounting/qbd/advanced/QuickbooksDesktopAdvancedPage.tsx Line 28 in 992e5d4
as 2nd param ( Lines 1286 to 1298 in 992e5d4
|
I don't think the frontend needs to send The steps described in the issue look incomplete
I think first we should clear that up. Which case is it? What triggers the sync? Case 1
Case 2
|
@johncschuster, @narefyev91, @ikevin127, @aldo-expensify Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
@aldo-expensify Just retested and the issue is still reproducible on both QBO and QBD, tested both on dev / staging API. Once the Lines 326 to 330 in 5f3782b
There were instances where Here are the details you asked for from my side - {
policyID: 18920FC1A9030899,
email: "[email protected]",
requestID: "8edefd622fd89648-SJC",
lastUpdateID: 3280895077,
previousUpdateID: 3269474291,
} then after the one above, {
requestID: "8edf0bccaec123a9-SJC",
lastUpdateID: "3280898069",
previousUpdateID: "3280895077",
} which turned |
Thanks @ikevin127 , I'll investigate again later this week with the information you provided 🙇 |
@johncschuster, @narefyev91, @ikevin127, @aldo-expensify Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
How's this going, @aldo-expensify? |
Thanks for the ping.. investigating now:
I can confirm that the setting is being set to
In those logs, I can see that the Integration Server is turning back on the autoSync setting. The only place that can happen for QBO I believe is here: So that narrows down the problem to figuring out why the Integration Server is considering that the policy has never been configured before. |
@aldo-expensify This is a known issue, but you ca get around it by simply removing the |
I'm pretty sure the issue is not the |
There seems to be a problem with the Integration Server in my dev env, since the URL that ends up with |
Oh, yes - I confused it with what I'm doing when connecting QBO on DEV. |
I'm still trying to fix my dev environment to work on this, I'm asking here: https://expensify.slack.com/archives/C3BGN04K1/p1734356547490549 |
I was just able to fix my dev environment, so I'll be able to resume my investigation / debugging today |
@ikevin127 did you add the QBO connection from Old Dot? or New Dot? I didn't find in the logs a call from your account to |
No idea whether the very first time was from OD, but after that I disconnected and re-connected multiple times all from ND. |
I'm referring to this specific time you tested: #52132 (comment) . If you connected to QBO that same day for testing, from looking at logs, I think it wasn't through New Dot. |
Makes sense, let me try this on a fresh account with connecting directly from ND to make sure I didn't go through OD flow initially, then and check whether the issue is still reproducible - will pass the details regarding policyID and all other from the fresh try. |
Did as mentioned in the comment above and the issue is not reproducible if the connection flow is done strictly on ND, here are the details from {
policyID: C6E8EC51B5025647,
email: "[email protected]",
requestID: "8f44e0e189a9cf1b-SJC",
lastUpdateID: 3487737068,
previousUpdateID: 3487736201,
} Tried both with test emails (using +) and non-test and was not able to reproduce when connection was made from ND. |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Version Number: 9.0.58-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/5184320
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause - Internal Team
Action Performed:
Precondition: QBD connection is established in the workspace.
Expected Result:
Auto-sync toggle is disabled
Actual Result:
Auto-sync toggle returns to enabled after sync finishes
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6656487_1730891945304.Screen_Recording_2024-11-06_at_2.08.24_in_the_afternoon.1.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: