My self and others on the forum post below have been effected by the breaking of the dropbox support in rclone when no change happened on the rclone side suggesting an API change on the dropbox side.
https://forum.rclone.org/t/failed-to-open-source-not-an-encrypted-file-bad-magic-string/37790/7
I was wondering if anyone knows what API was changed or broken and if it is a temp or perm change. That way we would know if we need to wait for rclone to work around the issue or if we need to wait for dropbox to fix it. It seems to effect current and past versions of rclone.
I know 3rd party apps are not supported but i am not sure where to go to find the change notes for your API's and online support did not know either.
Expected Response Headers:
HTTP/1.1 206 Partial Content
---
accept-ranges:bytes
Content-Length:26397831
Content-Range:bytes 0-26397830/26397831
content-type:video/mp4
Actual Response Headers:
HTTP/1.1 206 Partial Content
---
accept-ranges:bytes
Content-Length:26397831
Content-Range:bytes 0-26397830/26397831
content-type:application/grpc
