There is a bug in WIN image download

[cns1rius]

Describe the bug

当点击图片下载按钮时，并保存到部分非默认位置时(例如C:\Users\xxx\Documents、C:\Users\xxx\OneDrive\图片等)，会报错："找不到文件。请检查文件名是否正确，然后重试。"
下载文件应该是先检查是否有该文件，如果没有则新建该文件并将内容拷贝进新文件，而我怀疑目前的下载操作只是直接将内容拷贝，而忽略掉了该文件是不存在于该目录的，请检查代码逻辑。

Feed Info

I'm @s1rius
下面是bug截图

Reproduction Video

No response

Environment

Environment

App Version: 0.1.2-beta.0
OS: Windows
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Follow/0.1.2-beta.0 Chrome/130.0.6723.44 Electron/33.0.0 Safari/537.36
Env: electron
Browser: Chrome

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.

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!)

[linear]

FOL-779 WIN端图片下载出现bug

[github-actions]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

FOL-779 WIN end image download bug

[github-actions]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

Describe the bug

When clicking the image download button and saving it to some non-default locations (such as C:\Users\xxx\Documents, C:\Users\xxx\OneDrive\Pictures, etc.), an error will be reported: "Cannot be found" file. Please check that the file name is correct and try again."
To download a file, you should first check whether the file exists. If not, create a new file and copy the content into the new file. However, I suspect that the current download operation just copies the content directly and ignores that the file does not exist in the directory. Yes, please check the code logic.

Feed Info

I'm @s1rius
Below is a screenshot of the bug

Reproduction Video

No response

Environment

Environment

App Version: 0.1.2-beta.0
OS: Windows
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Follow/0.1.2-beta.0 Chrome/130.0.6723.44 Electron/33.0.0 Safari/537.36
Env: electron
Browser: Chrome

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.

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!)

[follow-reviewer-bot]

This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. If you have any new additional information—in particular, if this is still reproducible in the latest version of Follow or in the beta—please include it with your comment!

[follow-reviewer-bot]

This issue has been automatically closed due to inactivity. If this is still an issue, please feel free to reopen it or create a new one.