Question: (null) (IMG_E117#.JPG)... operation couldn't be completed, (com.apple.ImageCaptureCore error -9937.)
My client and I ran into a weird import new photos problem with his iPhone 6+ (iOS v11.1.0) with his updated Mac OS Sierra v10.12.6's Photos. There were a couple images that failed to import, but it did import other new ones though. He has thousands of images and several videos in his iPhone and 13.3" 2012 MacBook Pro (MBP). MBP's Photos app showed a couple "(null) (IMG_E117#.JPG)" (# was the 6 and 7) ... "operation couldn't be completed, (com.apple.ImageCaptureCore error -9937.)" errors -- http://picpaste.com/pics/2Null-IMG_E117xJPGerrors-CRZF1LTz.1510369699.gif for a screen shot/capture of it.
I did some digging. I remember in Windows, iPhone would mount and connect as a drive to view its DCIM files. I didn't know how to do that in Mac OS (how?). I connected and looked in its DCIM and found the two offending images. They had their *.AAE files to modify the photos in iPhone. I noticed they were modified recently last month according updated 64-bit Windows 7's Explorer, but 64-bit IrfanView v4.5.0 said they were taken in October 2015 according to their EXIF datas. Anyways, I copied those two images and told him to delete those two images. Photos app was able to import without them. I also noticed he already had those two photos in his Photos app.
Now, what the frak happened? This had never happened before. Did iOS v11 break something and caused this? Is it a known bug? We upgraded his iPhone 6+'s iOS several weeks ago from the latest v10.3.3 to v11.0.3 to v11.1.0 (did not get yesterday's v11.1.1 yet) if I remember correctly.
Thank you in advance. 🙂
iPhone 6 Plus, iOS 11.1, Verizon Wireless & mac OS Sierra