How do I import photos from my iPhone 4S into Aperture 3.2

Do you have any import settings enabled that may prevent showing the photos? I assume since you took new photos and reconnected it wasn't a duplicates issue, but do you have any other import settings?

Also, have you tried importing with iPhoto?

I have the same problem since the last Aperture update. It's inappropriate for people to suggest using Image Capture and iPhoto - they might be workarounds but Aperture should *work* with the iPhone and any camera - it used to before the last update.

My workaround is to quit Aperture, unplug the phone, replug the phone and then relaunch Aperture.

And if that doesn't work, unplug/quit, and start with Aperture open first and then plug in the phone again.

It's broken - plain and simple, and I hope it's addressed in the next update.

I wasn't suggesting iPhoto as a workaround, I was seeing if the results were different using iPhoto. Just trying to do a little troubleshooting. 🙂

Do you have Photo Stream enabled (iCloud feature)?

@Shuttersp33d: Sure, I appreciate that, but those of us who are using Aperture probably don't want to use iPhoto. In my case, the fact that Aperture launches when I connect my iPhone (correct behaviour as configured in Preferences) and iTunes recognizes my phone suggests that the problem is within Aperture recognising the device.

@AppleMan1958: Yes I do have Photo Stream enabled. When I disable that, it seems to work!? So this must be the root of the problem. Do you know any more about this phenomena? Thank you!

Just found this, though I am running 3.2.2 it seems the issue is not entirely resolved. This mentions a slightly different problem with Photo Stream but perhaps it reinforces the idea that the interface is buggy.

http://aperture.maccreate.com/2011/12/12/aperture-3-2-2-addresses-hidden-photost ream-issue/

If you have PhotoStream enabled, you already have imported the photos, and there is no reason to import them again. This is a great feature of Photostream. If you wanted to import them again, for some reason, you should uncheck the box that says Hide Photos Already Imported.

When you have PhotoStream enabled, the photo from your iPhone will go into the Camera Roll as usual, abd then will be uploaded into the PhotoStream.

Aperture will automatically import the photo in PhotoStream into an Aperture project corresponding to the month. For example, for photos taken in December, they are in a project called Dec 2011 Photo Stream. All Photo Stream photos go there, although I believe you could move them to a different Album later if you choose.

Hi again AppleMan1958. You are my hero! Thanks for the advice. Aperture seems to be importing photos into a special Library section called "Photo Stream" rather than projects... and not all of my recent photos are showing up, but I'm imagining that a bit of sync-catch-up and tweaking will fix things. I really appreciate the help.

Everything in Aperture goes into a Project, even stuff from Photo Stream. Here is a hint. Right-click on one of the photos in Photo Stream and select Show In Project.

This is ok if you are a low volume user, or are wanting to access photos soon after they are taken, but no good otherwise.

Photostream imports the last 30 day's worth, but it also only holds a maximum of 1000 photos, and includes shots from all sources. Thus, you fill it up quickly if, say, you add shots from a DSLR loaded to Aperture via a card. You are borked (as I am at present) if you want to access a photo that is on an iPhone but older than the last 1000 photos imported to Photostream.

This is the first time I have needed to download from the Phone for a while, but when attached by USB cable, Aperture used to offer the iPhone as an option in the "Import" list. Damned if it will now, and that looks as if Apple have assumed the Photostream just makes imports by wire unecessary for anyone using Photostream. Not the real world. I think it's a point Appleman1958 misses, too.

Tom

Though I should add that repeatedly plugging and unplugging the iPhone eventually gets Aperture to recognise it. This suggests that there is a bug somewhere, because this is evidently not only my own experience.

Tom