can't access vintage backblaze B2 bucket with new cyberduck cli

[Buster-Else]

Have used an upload program for years that invokes cyberduck cli ver. 6.6.2 to upload files to backblaze B2. After upgrading computer from Win 10 to Win 11 and re-installing Cyberduck cli ver. 9.2.0, I get "file not found" errors when uploading to an old bucket created before May, 2020. Newer buckets still work ok.
Backblaze says any bucket created before May, 2020 is not S3 compatible. Is this a problem?

[dkocher]

I suspect you are connecting using the native Backblaze B2 protocol implementation such as duck --list b2:/ which does make use of the S3 interoperability layer.

[Buster-Else]

Here is an example of the command I am using:
"cmd /C duck --username .........b89b --password ........................................................................................c1ef --upload b2://periodicals/RUS-Beresan_Dist_Odessa_Nwsltr/Vol_01-1996-97/ c:\ToBeUploaded\RUS-Beresan_Dist_Odessa_Nwsltr\Vol_01-1996-97\Issue_02-Oct.pdf --existing overwrite"

[Buster-Else]

I created a new backblaze B2 bucket and ran the above command (with the new bucket name) and it also failed with a "file not found" error, so the issue is not the age of the bucket. Rather, it seems to be related to the number of subfolders in the target. I modified the above command to:
"cmd /C duck --username ..........b89b --password .......................................................................................c1ef --upload b2://periodicals/RUS-Beresan_Dist_Odessa_Nwsltr/ k:\ToBeUploaded\RUS-Beresan_Dist_Odessa_Nwsltr\Vol_01-1996-97\Issue_02-Oct.pdf --existing overwrite"
(The "Vol_01-1996-97/" subfolder has been removed from the target path). This command works!
So, the newer versions of cyberduck cli no longer handle subfolders in the target path, Was this intentional?