Aperture 3.24 crashes after update

If you bought it on the Mac App Store and somehow something went wrong (it sorta looks like this is the case), you don't need to use Time Machine at all.

Just delete Aperture from your Mac (select it in Finder, press command-Delete, and then enter your password. Or on Lion you can just click and hold in Launchpad and press the X in the upper left when it starts wiggling).

Anyway, then go to the Mac App Store, click the purchases tab, and re-install Aperture.

That crash log is very typical: The PluginManager.framework is missing from your System Library. For this particular framework this happens in most cases by installing Final Cut. Have you Final Cut installed?

The recommended, safest solution to fix the library is to reinstall the operating system, using the latest combo update from the support downloads page , see this Support article:

Aperture 3.x: Aperture unexpectedly quits if Final Cut Express 4 is installed:

http://support.apple.com/kb/TS3528

It might be less trouble, to replace just the /Library/Frameworks/PluginManager.framework from the latest Time Machine backup, before the trouble started (if you indeed did install Final Cut), but the recommended procedure is to reinstall the OS.

Regards

Léonie

So, if the update broke that file, then an app reinstall won't fix it.

No, the MacOS update does not corrupt the Plugin Manager Framework. Installing other Applications may do it. See my post above - did you install any other multi media Applications?

If you are on a very slow network, reinstall the Framework from the Time Machine Backup. That has been proven to work previously. To find the Library quickly when diving back in time on your Time Machine add it to the Finder Sidebar before opening Time Machine.

I am glad you could restore the missing framework. As for the reason, why it went missing:

In your first post post you wrote:

Today I accepted a bunch of software updates, including one for Aperture.

Was a "Final Cut" update one of the updates you accepted?

The date on the corrupted PluginManager file was 2006.

The date on the one in the backup was 2010.

The date on the corrupted PluginManager file matches my Final Cut Pro installation (early 2007); The date on the one in the backup matches all three of my current installations (iMac, MBP).

Do you have Aperture plug-ins installed? Some have relatively old code.

But as you do not remember exactly which applications are newly updated, it is hard to guess, what reinstalled the outdated framework.

Last night I installed the OS 10.8.2 on both my iMac Quad Core and MacBook Pro without incident, then the Aperture 3.4 update. Upon the first launch on my MacBook Pro, I got a warning that I must run Photo Library First Aid (Repair Database was the preselected choice). Now it seems to run OK there. On the iMac, the library seems to remain corrupted even though I performed the repair, ran the Mac disc utility, and Onyx.

My question is: did the library itself get corrupted, or is it a glitch in the app upgrade?

Frozenfire – How is your library corrupted? What are you seeing?

At launch, Aperture shows the usual "Opening Aperture Libraries". Then an error message pops up which says, "Aperture Quit Unexpectedly" along with a lengthy report. It states that the message will be sent to Apple automatically. If I keep re-launching, a pane opens which invites me to repair the Aperture Library. When I activate that, it goes to completion and then Unexpectedly Quits again.

I'm not that well versed with Time Machine, but following the instructions in my two Mountain Lion handbooks I was able to find a time yesterday prior to downloading the Aperture update. I restore from that time and it makes an "original" version of the Aperture icon. When I try to launch that, a pane opens which says "Aperture Library can't be loaded because it is from a newer version of Aperture." These error messages keep alluding to the library, not the app itself, that's why I'm confused.

The good news is that when I run iPhoto and click Show Aperture Libraries, I can see all the RAW images I have stored in Aperture, so I know they're still there.

With all these error messages that are automatically being sent to Apple by me and others, I hope they publish a fix for this glitch. My work depends on these images!

Have you tried deleting and reinstalling Aperture yet? That fixes most similar issues that have been posted around here, and it solved that issue on my machine.

No, not yet. I read some earlier comments regarding delete and re-install, but my concern is whether or not so doing will delete my images. Are the images and the program itself in different places? I'll be happy to try deleting and re-installing if it's safe to do so.

This brings up the obvious question, if I go to the Apple store and re-install, should I avoid the 3.4 update until the fix has been published? And being a curious person, I'd like to know why this occurred on my iMac and not my MacBook Pro?

Thanks in advance for your help.