FileReader cannot read iCloud drive files selected with <input type="file"> in iOS 9 Repro Case: http://jsbin.com/yucavaxiyufi/1/ Repro Steps: a. Open above repro case on iOS 9. b. Select a file from iCloud drive. c. Watch the read fail with error code 4: FileError.NOT_READABLE_ERR. Possibly related to Bug 136117.
<rdar://problem/23796609>
Bundles selected from iCloud Drive should be zipped as they are on the Mac. There's an existing radar for this that I don't have on hand right now. Non-bundles such as text files selected from iCloud Drive are readable for me using FileReader on 9.1. Can you confirm that that's the case for you as well, Warren?
This is actually Radar <rdar://problem/19009562>
Basically, the changes in Bug 132713 need to be done on iOS as well.
(In reply to comment #2) > Bundles selected from iCloud Drive should be zipped as they are on the Mac. > There's an existing radar for this that I don't have on hand right now. > Non-bundles such as text files selected from iCloud Drive are readable for > me using FileReader on 9.1. Can you confirm that that's the case for you as > well, Warren? I'm using iOS9.1 and tried to select a .numbers file. It's giving an error code 4.
This is the same issue I have ticketed. https://bugs.webkit.org/show_bug.cgi?id=173548 I believe I narrowed down the issue a little further. If a file is in a users iCloud but was never accessed on the mobile device then uploading it via a file input will throw the error. However, if the file is viewed/opened in another application first then the file will upload. We get dozen of these issues a day on our application. Each time it's a user uploading a file from iCloud. These are résumé files they created on their laptops and then access on their phone for applying to job openings.
*** Bug 173548 has been marked as a duplicate of this bug. ***
I'm also seeing this code 4 error whilst attempting to read images with fileReader from users on ios 11.4.1
The fix for this issue was needed outside the WebKit project, therefore this is being resolved as 'Moved'. This should now be fixed in shipping software.