When I try to run: clone bisync "OneDrive Business": ~/OneDrive\ Business --verbose --resync
I get Failed to create file system for "OneDrive Business:": failed to configure OneDrive: json: cannot unmarshal string into Go value of type oauth2.Token
Run the command 'rclone version' and share the full output of the command.
Which cloud storage system are you using? (eg Google Drive)
OneDrive - both onedrive personal and onedrive business (not SharePoint, haven't tried that) give the same error. Google Drive works absolutely fine with the same command.
The command you were trying to run (eg rclone copy /tmp remote:tmp)
rclone bisync "OneDrive Business": ~/OneDrive\ Business --verbose --resync
The rclone config contents with secrets removed.
Current remotes:
Name Type
==== ====
Google Drive drive
OneDrive Business onedrive
OneDrive Personal onedrive
A log from the command with the -vv flag
2023/08/31 19:17:44 DEBUG : rclone: Version "v1.63.1" starting with parameters ["rclone" "bisync" "OneDrive Business:" "/home/jez/OneDrive Business" "--verbose" "--resync" "-vv"]
2023/08/31 19:17:44 DEBUG : Creating backend with remote "OneDrive Business:"
2023/08/31 19:17:44 DEBUG : Using config file from "/home/jez/.config/rclone/rclone.conf"
2023/08/31 19:17:44 Failed to create file system for "OneDrive Business:": failed to configure OneDrive: json: cannot unmarshal string into Go value of type oauth2.Token
2023/09/01 09:16:47 DEBUG : rclone: Version "v1.63.1" starting with parameters ["rclone" "lsd" "OneDrive Business:" "-vv"]
2023/09/01 09:16:47 DEBUG : Creating backend with remote "OneDrive Business:"
2023/09/01 09:16:47 DEBUG : Using config file from "/home/jez/.config/rclone/rclone.conf"
2023/09/01 09:16:47 Failed to create file system for "OneDrive Business:": failed to configure OneDrive: json: cannot unmarshal string into Go value of type oauth2.Token
I should probably add that prior to trying to do all this, I hadn't used this machine to connect to any of my remotes for some time, so the tokens had expired. I requested new tokens for all of them, so maybe it seems that the google one worked but the MS ones didn't? Not sure if this is something wrong at MS's end or yours?