You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Aperture 3.3.2 unresponsive if library contains old iPhoto albums - solution

Aperture 3.3.2 introduced the "Keep Projects & Albums arranged by : Date" function. At last! but sadly this new feature can cause problems including unreponsive projects and albums, failure to launch and crashes.


This appears to be due to albums imported from iPhoto at some point in the past, which do not support the date function and cause the sort function to fail silently.


If you are having problems with aperture 3.3.2, check the Console application in OSX to see if warnings appear when you select "Keep Projects & Albums arranged by : Date":


8/6/12 6:22:32.589 PM Aperture: [<RKAlbum 0x1240e7a20> valueForUndefinedKey:]: this class is not key value coding-compliant for the key minImageDate.


This indicates you have the same problem I have. The solution is to remove or replace these albums in your library by creating new albums (do not use 'duplicate album').


If you can't remember which albums are iphoto albums, you can use gdb in xcode to get the album names:


In the Activity Monitor Application, find the PID of Aperture (type aperture in the search box and check the first column)


In the Terminal Application, run the following.


/Applications/Xcode.app/Contents/Developer/usr/bin/gdb /Applications/Aperture.app/


Then type


attach <PID of Aperture>


Then when it finishes loading symbols, type


print-object 0x1240e7a20


Where the number (0x1240e7a20) is the same as the one in the console error message.


For example:


(gdb) print-object 0x1240e7a20

<RKAlbum: 0x1240e7a20 > modelId = 4627, uuid = '+i7gr2x0SFyR8ifpB2a6dw' name='iphoto dupes 4', displayName='iphoto dupes 4'


Then type


c


to continue execution of aperture, locate the album (e.g.) iphoto dupes 4, and then select all photos in the album, select new->album, type the new name (can be same as old name) then delete the old album.


Repeat this until all bad albums are gone.


If you have many, this will be a LONG process, and you are likely to encounter crashes along the way - bad luck!

Macbook Pro, Mac OS X (10.6)

Posted on Aug 6, 2012 10:59 AM

Reply
19 replies

Aug 6, 2012 11:22 AM in response to AlexBrown

Great discovery, Alex,

thanks for posting this.


I have similar problems and tried your fix, but for me the debugger only turns up the name of my previous camera for some reason, no iPhoto albums.


Console.app:

06.08.12 20:04:25,979 Aperture[9051]: [<RKAlbum 0x1171c6bd0> valueForUndefinedKey:]: this class is not key value coding-compliant for the key minImageDate.

gdb:


print-object 0x1171c6bd0

<RKAlbum: 0x1171c6bd0 > modelId = 576, uuid = 'KTxJyhwER8yx48TrV824IA' name='FZ 50', displayName='FZ 50'


Any idea, why Aperture might be complaining about my old Lumix FZ 50 r.i.p.?


Cheers

LĂ©onie

Aug 6, 2012 8:39 PM in response to AlexBrown

I just had an additional idea.


I migrated from iPhoto to Aperture a year ago or more, and haven't used iPhoto since. I just noticed my iPhoto was back on 8.x and now there is 9.3 something.


I'm going to try upgrading iPhoto, and opening the iPhoto library in the latest iPhoto, and see if that improves anything. Probably a shot in the dark, but been meaning to check out iPhoto anyway now that everything is supposedly "unified" maybe my wife will still use iPhoto.

Aug 22, 2012 11:19 PM in response to AlexBrown

You sir are a certifiable genius!


One thing that may help in the debugging process where multiple albums are needed to be erradicated.


While in terminal, after typing "c" to continue:

type

^c (that is hold down the control key and the c key)

then type

detach <PID of Aperture>

then type

quit


That allowed aperture to keep going without having to quit and restart it.


Once Aperture is running, keep repeating the "Keep Projects & Albums arranged by : Date" process and note the object number that appears in the console and then kill that album from within Aperture. Eventually, you'l get them all. You'll know you've got it when console messages stop appearing and when keeping albums arranged by date actually does just that in your library.


For me, the issues were all related to Smart Albums I had created. Made it somewhat easier as they were easy to just delete. I can recreate them later if I need to.

Aug 22, 2012 11:30 PM in response to AlexBrown

Alex: In the library just repaired using your method, I still have one issue. If I go to add a new vault, the dialog box pops up that says:


"1 managed file will be included in this vault.


16628 referenced files will not be included. These need to be backed up separately.


Vaults provide automated backup of all original files stored inside your Aperture library. Original files for referenced images are stored elsewhere, and are not backed up in vaults.


Adjustments, ratings, and other metadata are included for all images, regardless of file location."


Thing is, all the master files related to this library are (supposed to be) referenced only. I create a Smart Album to catch only Managed Files and it comes up empty.


Any thoughts on how to locate, so I can then relocate, the 1 managed file hiding in the library?

Aug 30, 2012 3:22 PM in response to AlexBrown

Hi, was hoping to have found the solution as to why Aperture keeps crashing on me when doing basic stuff like clicking on "New Smart Album" but unfortunately I seem to be less lucky.


Console gives me


*** Terminating app due to uncaught exception 'NSUnknownKeyException', reason: '[<RKAlbum 0x11fdc99e0> valueForUndefinedKey:]: this class is not key value coding-compliant for the key minImageDate.'


So it does look very similar to what is described here and I did import iPhoto libraries with albums and smart albums (multiple iPhoto libraries even and some of them twice at that... don't ask 🙂)


Unfortunately gdb gives me


(gdb) print-object 0x11fdc99e0

0x11fdc99e0 does not appear to point to a valid object.


I might be doing something wrong or I might have another issue altogether perhaps... any input is appreciated, thanks!

Aperture 3.3.2 unresponsive if library contains old iPhoto albums - solution

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.