Skip to content

Unable to save successfully to Readwise #3312

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

Closed
3 of 5 tasks
lazydao opened this issue Mar 27, 2025 · 7 comments · Fixed by #3497
Closed
3 of 5 tasks

Unable to save successfully to Readwise #3312

lazydao opened this issue Mar 27, 2025 · 7 comments · Fixed by #3497
Assignees
Labels
bug Something isn't working platform: desktop

Comments

@lazydao
Copy link

lazydao commented Mar 27, 2025

Platform

Desktop - Windows

Describe the bug

Image

Relevant Information

[2025-03-27 11:54:46.587] [error] (main) Error: Command failed: "C:\Users\admin\AppData\Local\Folo\app-0.3.13\resources\app.asar\node_modules\fast-folder-size\bin\du64.exe" -nobanner -accepteula -q -c .
The system cannot find the path specified.

at genericNodeError (node:internal/errors:984:15)
at wrappedFn (node:internal/errors:538:14)
at ChildProcess.exithandler (node:child_process:422:12)
at ChildProcess.emit (node:events:518:28)
at maybeClose (node:internal/child_process:1104:16)
at ChildProcess._handle.onexit (node:internal/child_process:304:5)

[2025-03-27 11:56:21.868] [info] (main) PushReceiver ready

Reproduction Video

No response

Environment

Environment

App Version: 0.3.13
OS: Windows
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Folo/0.3.13 Chrome/132.0.6834.196 Electron/34.2.0 Safari/537.36
Env: electron
Browser: Chrome
Session Trace Id: efdt0Luo4Yn9a-ez_-1EL
Renderer: 0.3.13

Validations

  • Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
  • Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
  • This issue is valid

Contributions

  • I am willing to submit a PR to fix this issue
  • I am willing to submit a PR with failing tests (actually just go ahead and do it, thanks!)
@lazydao lazydao added the bug Something isn't working label Mar 27, 2025
Copy link

linear bot commented Mar 27, 2025

@lazydao
Copy link
Author

lazydao commented Mar 28, 2025

Supplementary Error Log:

Access to fetch at ' https://readwise.io/api/v3/save/ ' from origin ' app://follow.is ' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: The 'Access-Control-Allow-Origin' header has a value ' https://readwise.io ' that is not equal to the supplied origin. Have the server send the header with a valid value, or, if an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

@lawvs lawvs self-assigned this Mar 28, 2025
@lawvs
Copy link
Member

lawvs commented Mar 28, 2025

I am unable to reproduce this issue, as I can save to Readwise correctly. Do you have any additional settings that might affect this, such as a proxy?

Image

@GladioFeng
Copy link

same issue

Image

@lazydao
Copy link
Author

lazydao commented Mar 29, 2025

I am unable to reproduce this issue, as I can save to Readwise correctly. Do you have any additional settings that might affect this, such as a proxy?

Image

I tried to close the proxy before proceeding, but the problem persists.
To add, I had the problem after upgrading to Folo, which cleared the integration data I had previously saved, so I retrieved the token and filled it in again.

Image

If there is anything else I can offer, please let me know.

@ifeitao
Copy link

ifeitao commented Apr 15, 2025

same issue in macos after update to folo.

@lawvs
Copy link
Member

lawvs commented Apr 15, 2025

Thank you very much for providing the information; this issue will be fixed in the next version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working platform: desktop
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants