I've got multiple reports from users about problem after updating to iOS 10.3.
Users can't access files that are transferred using iTunes file sharing after upgrading to iOS 10.3.
This problem doesn't happen when transferring files with only alpha numeric characters.
Bug was present when transferring file names with Korean and Japanese.
It transfers without any problem and shows up correctly in iTunes(file sharing).
But the file is not accessible from the app.
The file is listed in NSFileManager::contentsOfDirectoryAtPath.
But when checking the file with NSFileManager::attributesOfItemAtPath
it fails with
Error Domain=NSCocoaErrorDomain Code=260 "The file “KoreanJapaneseCharacters.txt” couldn’t be opened because there is no such file." UserInfo={NSFilePath=/var/mobile/Containers/Data/Application/0353E581-F595-4E83-83C0-AAFBF4589A8A/Documents/KoreanJapaneseCharacters.txt, NSUnderlyingError=0x17025d880 {Error Domain=NSPOSIXErrorDomain Code=2 "No such file or directory"}}
( Had to replace filename because this website doesn't seem to like foreign characters. )
The bug is not reproducible on my devices, but I got the error message using a TestFlight build from a bug reporter.
And files transferred before the iOS 10.3 update (with foreign characters) doesn't have problem accessing. And transferring english file names and then renaming to Korean file names inside the app works without problem.
Anyone got similar bug reports? I would love to fix the problem, but not sure what I can do to fix it.
I think it has something do with the APFS update.