This isn't something we've been able to reproduce in tests. The behavior is the same regardless of the file name, though the behavior may differ between file types. (For example, if you can't handle a zip file, you'll get the error but it doesn't matter what the file name is.)
I've attached 2 PDFs and 2 zips to demonstrate this. The behavior should be the same for each "set", though the behavior between PDF and zip may differ.
Note that realistically, any fix here would need to be done in iOS as there's an RFC for how to handle non-ASCII filenames like this and we are following it.