Hello, I've found this bug and I believe it could be an underlying reason for many of the issues that have come up where people cannot get the downloads to start.
On both the Mac and Windows versions of BORG, if the download directory doesn't exist, the download won't start. And the default download directory that is set immediately after install is one that will not exist yet, so this problem always occurs until the download directory is created or changed to an existing one.
There is no error message warning the user of the nonexistent download directory. There is also no error reporting why the download cannot start. In the Windows version, the downloader just skips to the next file in the download queue. In the Mac version, the downloader gets stuck in the "Verifying" step of the first download in the queue and never progresses beyond that.
In both cases, creating the download directory fixed the problem for me. A simple warning message that the download directory doesn't exist (and perhaps prompting to create it for them) would notify the user that this is the problem. I hope this is an easy fix for you and something that will spare people some confusion in the future!
Hello, I've found this bug and I believe it could be an underlying reason for many of the issues that have come up where people cannot get the downloads to start.
On both the Mac and Windows versions of BORG, if the download directory doesn't exist, the download won't start. And the default download directory that is set immediately after install is one that will not exist yet, so this problem always occurs until the download directory is created or changed to an existing one.
There is no error message warning the user of the nonexistent download directory. There is also no error reporting why the download cannot start. In the Windows version, the downloader just skips to the next file in the download queue. In the Mac version, the downloader gets stuck in the "Verifying" step of the first download in the queue and never progresses beyond that.
In both cases, creating the download directory fixed the problem for me. A simple warning message that the download directory doesn't exist (and perhaps prompting to create it for them) would notify the user that this is the problem. I hope this is an easy fix for you and something that will spare people some confusion in the future!