"Item already exists" when moving image into subfolder with a question mark in its name

[CMB_photosnapper]

When I'm trying to move an image in the "content" tab into a subfolder with a special character in the name ("subfolder?"), I get an errormessage telling me that the "item already exists". 
When I click on Auto-Resolve it simply changes the name of the image by adding a " (1)" without moving the file - even though there's no other image with the same file name.

What I've already tested:

Moving it in the finder in macOS works.
Moving it in other applications works. 

Opening the file, editing the file and saving the file works. 

So the file is not corrupt.

This happens with all files.

When I remove the question mark from the folder name ("subfolder") it works. 

Looks like Brige is puzzled by a folder name with special characters - certainly a bug and not a feature. 

[Lumigraphics]

Bridge apparently doesn't work with characters that are illegal on either Mac or Windows filesystems. Question mark is reserved on Windows, you'll have to remove that to use the folder in Bridge.

[CMB_photosnapper]

So I can create a subfolder in Bridge with a name like "subfolder?"and I can access it in Bridge.

But I can't move files in or out of that folder in Bridge.

On the other hand it works perfectly fine for Finder, Preview, Photoshop, Helicon Focus, CaptureOne and just about every other app I can think of.

That doesn't sound very logical to me, if Brige doesn't work in a folder with a special character it should not allow me to create one.

Why doesn't Bridge show an error message while creating the folder to begin with?

[Lumigraphics]

I don't work for Adobe and can't answer "why" questions. I just know that I've seen other posts about this. Bridge is cross-platform and has mostly identical features, so its not a huge surprise. We see Windows limitations in Adobe's Mac software and Mac limitations in Adobe's Windows software, so I guess it evens out in a way.

As for the "it shouldn't have this bug", well, stand in line. There are quite a few bugs lurking about.

[CMB_photosnapper]

Good point - I think you're spot on with the Windows/Mac limitations, maybe it relies on the OS to give a warning while creating the folder (if I remember correclty you get one in Windows) but since it works for macOS there's no warning.

And regarding the bugs - yeah, I know most of them only too well - especially in the new version.

I hope they can get some of them fixed, performance-wise it's definitely not as good as 22.