Photos refuses to import JPEGs

Thank you for the suggestion. The HDD holding the library is Mac OS Extended (Journaled).

I opened one of the troublesome images in Preview and pressed Save and then reimported it but got the same error message.

When I exported it from Preview I was able to import it. Given that I need to import a large amount of images that will unfortunately not work as a solution. But perhaps it indicates something?

Edit: In Get Info both the original and the exported file appear identical.

Thank you very much for the suggestion, that's an interesting idea I hadn't thought of.

Sure thing, does this work? I put one of the JPEGs and it's AAE file in a shared iCloud folder.

https://www.icloud.com/iclouddrive/06dtDoMPk4Xveti8w28JcoahA#photosimportproblem

Thank you very much for testing Léonie. Your reply caused me to try this further. It appears that the AAE file remains linked somehow to the JPEG whether it is dragged with the JPEG or not. Like you discovered that link will be broken if the AAE is renamed. The link also breaks if the AAE is moved out of the folder or deleted before the JPEG is dragged into Photos.

I've emailed Hipstamatic support to see if something could be done to keep the edits in the AAE file. I'll updated the thread when they reply.

cheers

philip

Thank you Matti, that is really interesting. Let's hope Apple fixes it.

This is something I've been looking at also. I've been trying to figure out why some AAE files are troublesome whereas others, which also emanate from the Hipstamatic app, are not.

There are a few strings in them which differ, apart from <data>. On an AAE file that does not cause trouble, the end looks like this:

<key>adjustmentEditorBundleID</key>
<string>com.apple.mobileslideshow</string>
<key>adjustmentFormatIdentifier</key>
<string>com.apple.photo</string>
<key>adjustmentFormatVersion</key>
<string>1.2</string>

...whereas on a troublesome AAE file it looks like this:

<key>adjustmentEditorBundleID</key>
<string>com.syntheticcorp.hipstamatic</string>
<key>adjustmentFormatIdentifier</key>
<string>com.hipstamatic.Photo</string>
<key>adjustmentFormatVersion</key>
<string>1.0</string>

But editing the former file to match the latter – either string by string or pasting in the whole bit at the end – still causes the error upon import.

Thank you for the suggestion. I created the app on the Desktop. The resulting file will, when dragged from the new location (Desktop), be imported.

But If I first remove the original image file from its original folder, move the Automator-created file into its place and then drag that new file into Photos, it will be rejected with the same error if the AAE file is present in that folder.

If I move the AAE file from that folder first the new file will be accepted by Photos. As I mentioned before this also happens with original image files.

I also moved the Automator app into the original image folder and tried the above, but the results were the same.

So it seems it is the presence of the AAE files which causes the error.