[Downloads Manager] Raycast cannot find the Downloads folder when using two macbooks with Raycast Cloud Sync

[rajath-ramakrishna-cruise]

Extension

https://www.raycast.com/thomas/downloads-manager

Raycast Version

1.86.0

macOS Version

Sonoma 14.7

Description

Using Downloads Manager on two different machines with two different usernames and that share the same Raycast config (using Cloud Sync) leads to one of them not being able to locate the Downloads folder.

So, setting the Downloads folder on one machine would make the other machine be unable to find the path to it and vice versa.

Steps To Reproduce

1. Get two macbooks with different usernames
2. Use Raycast sync on both
3. Install Downloads Manager extension
4. Set Downloads folder on Macbook 1
5. Go to Macbook 2 and try to use the Downloads folder and you'll be asked to set it. If you set it, then the next time use try to use Downloads folder on Macbook 1, you'll be asked to set it again.

Current Behaviour

This is the window you get when you try to access the Downloads folder on one machine when its location was set on another machine.

Expected Behaviour

Downloads folder must be accurately located on both machines, possibly by just following the ~/Downloads and not expanding the ~ because expanding that would include the username in the path (which would be different on two different machines) and I believe that's what is creating the conflict.

[raycastbot]

Thank you for opening this issue!

🔔 @thomaspaulmann @ron-myers @infused-kim @ridemountainpig you might want to have a look.

💡 Author and Contributors commands

The author and contributors of thomas/downloads-manager can trigger bot actions by commenting:

• @raycastbot close this issue Closes the issue.
• @raycastbot close as not planned Closes the issue as not planned.
• @raycastbot rename this issue to "Awesome new title" Renames the issue.
• @raycastbot reopen this issue Reopens the issue.
• @raycastbot assign me Assigns yourself to the issue.
• @raycastbot good first issue Adds the "Good first issue" label to the issue.
• @raycastbot keep this issue open Make sure the issue won't go stale and will be kept open by the bot.

[pernielsentikaer]

We had a look and this is an error in the API, I'll let you know when it's resolved

[raycastbot]

This issue has been automatically marked as stale because it did not have any recent activity.

It will be closed if no further activity occurs in the next 10 days to keep our backlog clean 😊

[pernielsentikaer]

This should soon be resolved if it's not already is, could you have a look @rajath-ramakrishna-cruise

[rajath-ramakrishna-cruise]

Yes, this has been fixed. Thanks much! Appreciate the quick resolution. 🙂