-
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
Accounting - Error shows up while connecting to Xero for the first time #42913
Comments
Triggered auto assignment to @twisterdotcom ( |
Triggered auto assignment to @Gonals ( |
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
|
@twisterdotcom 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. |
We think this issue might be related to the #collect project. |
Production bandicam.2024-05-31.12-43-07-730.mp4 |
Asking @lakchote or @hayata-suenaga if they want this: https://expensify.slack.com/archives/C036QM0SLJK/p1717152579841329 |
Given Xero isn't live for customers and you can just choose to sync it and resolve the error, I don't think this is a blocker though. Going to leave it as a Daily bug. |
We've fixed it here already: #42837. PR for it has merged. |
PAPOW |
PEWPEW |
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: **1.4.78-2
Reproducible in staging?: Y
Reproducible in production?: N
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-internal team
Action Performed:
Pre-requisite:
Expected Result:
No error message should show up while Xero is finishing up the setup
Actual Result:
"Couldn't connect to Xero" error appears while Xero is setting up the connection and the error message disappears after the connection is established
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Bug6497231_1717147151454.bandicam_2024-05-31_12-12-53-860.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: