You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 29, 2023. It is now read-only.
Maybe an unsuccessful connection attempt returns something that evaluates as truthy?
I am not sure if this is the best solution, but applying this patch fixes the problem
--- a/node_modules/@actual-app/api/connection.js+++ b/node_modules/@actual-app/api/connection.js@@ -41,6 +41,7 @@ async function init(socketName) {
// TODO: This could spawn Actual automatically. The ideal solution
// would be to bundle the entire backend and embed it directly
// into the distributed library.
+ initialized = false;
throw new Error("Couldn't connect to Actual. Please run the app first.");
}
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I am experiencing connection issues when the API client is invoked before Actual has started.
The problem occurs when doing the following
I have not investigated further, but I think this line might be a problem
node-api/connection.js
Line 34 in 91d69a7
Maybe an unsuccessful connection attempt returns something that evaluates as truthy?
I am not sure if this is the best solution, but applying this patch fixes the problem
The text was updated successfully, but these errors were encountered: