Closed IuliiaHerets closed 1 month ago
Triggered auto assignment to @joekaufmanexpensify (Bug
), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.
We think that this bug might be related to #wave-collect - Release 1
@joekaufmanexpensify FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors
Not overdue, will review today
@IuliiaHerets This is not a bug. It's an error message shown when we're unable to export a report to QBO. The error is being correctly shown as the account from which you submitted the report doesn't exist in QBO. If you create it there, or enable the setting referenced in the error, it would be resolved.
Closing for now, but please let me know if you have any questions about this!
@joekaufmanexpensify Thank you for explaining.
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number: 9.0.18-7 Reproducible in staging?: Y Reproducible in production?: Y If this was caught during regression testing, add the test name, ID and link from TestRail: https://expensify.testrail.io/index.php?/tests/view/4839855&group_by=cases:section_id&group_id=309135&group_order=asc Issue reported by: Applause Internal Team
Action Performed:
Expected Result:
I should be able to export the expense.
Actual Result:
Unable to export expenses to QBO "failed to export this report" message appears.
Workaround:
Unknown
Platforms:
Screenshots/Videos
https://github.com/user-attachments/assets/fa555851-d108-427b-8f48-ef19518674ab
View all open jobs on GitHub