Calling copyfile with remote control api alwaays fails with "malformatted" path error. The exact same inputs with a different protocol ( Google Drive, OneDrive ) suceeds.
Run the command 'rclone version' and share the full output of the command.
rclone v1.63.1
os/version: Microsoft Windows 10 Enterprise 22H2 (64 bit)
os/kernel: 10.0.19045.3324 (x86_64)
os/type: windows
os/arch: amd64
go/version: go1.20.6
go/linking: static
go/tags: cmount
Which cloud storage system are you using? (eg Google Drive)
DropBox
The command you were trying to run (eg rclone copy /tmp remote:tmp)
Note: The following is PowerShell code but I can also reproduce the same with C++ code.
Sure enough, removing the root "/" from the remote path in the copyfile rcd API call allows it to work.
In contrast, calling regular copy on the command line with the root "/" in place works without issue.
rclone.exe copy DropBox:/NewTestDir/TestFolder/1.txt C:/Data/DeletMe/DropBoxTest/1.txt
So this looks to me like an issue specific to the copyfile rcd API call.
If it's what it looks like, then, I would think the solution that allows the regular command line copy command to process the path with the leading "/" needs to also be applied to the copyfile rcd API call.
So as I was testing I can transfer files in any subdirectory by not having the leading "/"
ex.) DropBox:subfolder/test.txt ---> Works!
But I can't transfer files on the root in any case
ex.) DropBox:/test.txt ---> fails
ex.) DropBox:test.txt ---> fails
The other functionality like uploading/downloading, creating and renaming folders, works for these user's root path.
@Animosity022
Based on what you are saying how would one be able to format a path to transfer files to the user's "root" folder and not get it confused with the "root of the whole account" ?
@Animosity022
Thank for your patience and helping with this.
This is new to me, so I am slowly starting to understand.
So you are saying paths without "/" it tells DropBox it is the user running the command ( I assume it then knows to resolve the path relative to a "user space"? )
And paths with "/" resolve to the root of a whole account. If the user has access there it will work, if not, then not.
In the DropBox Browser Dashboard I can upload/download files to what "looks" like the root folder and it succeeds ( maybe that is the user's area "root" and not the whole account root?)
Rclone's command line I can do the same using "copy".
In my case I believe I have a personal account. I created it with a dummy gmail account and I am on the free-basic plan. I didn't do any further configuration.
My thinking is that I just need to know what to give copyfile so it will resolve the path to whatever the location is, that looks like the root in DropBox Browser Dashboard
So I am thinking:
1.) How can I confirm what the location is of what looks like the "root" in the DropBox Browser Dashboard?
2.) How can I confirm I have access to it? ( Or not! )
3.) For the copyfile API call, what does it need so that the path "DropBox:/test.txt" or "DropBox:test.txt" can be resolved to that location?