Will Aperture 3.6 work in Mac OS Sierra?

I had exactly same crashes.

iMac 27 Retina Late 2014

Macbook Pro 15 Late 2013

Do not use full screen mode to prevent "Crash and Black Screen"!

Repair or rebulid of aperture library can not fix the problem.

Just loaded Sierra and Aperture crashed right away. If you hit the full screen "F" key it seems to trigger the crash. Cannot get Aperture to turn on at all now, completely went to black screen

The Full Screen Mode is probably stored in the Aperture Preferences File.

Try, if you can get Aperture to launch again, if you reset the Preferences file as described here: https://support.apple.com/en-us/HT201289

Steps to reset preference settings

To reset your Aperture user preference settings to their original state, do the following:

1. Quit Aperture.
2. In the Finder choose "Go to folder" from the Go menu.
3. Type ~/Library/Preferences in the "Go to the folder" field. Press the Go button.
4. Remove the "com.apple.Aperture.plist" file from the Preferences folder.
5. Restart your computer if you're using OS X Mavericks (or newer)

The locations of your Aperture libraries are stored in the preference file listed above. If you have stored your library outside the default location of ~/Pictures/Aperture Library, make a note of where the library is before deleting the Aperture preferences file. If you have more than one library, you can bring up a dialog to choose which one to load by pressing Option immediately after you open Aperture.

You said it brother....

I think you have summed up the sentiments of many.

Aperture, C1 & Lightroom all have their strengths. I personally find Aperture to offer a very pleasing workspace & a joy to work with.

I have Capture One Pro (9.3), do I use it? I tinker with it but keep going back to Aperture.

Anyhow, we all know our days with Aperture will always be numbered....

I have returned my MacBook Air back to 10.11, of course Aperture is working again. I find a working Aperture much more appealing than what the features of Sierra has to offer me.

Maybe I'll get another year....

Maybe an update in Sierra will sort some of the current issues with Aperture.

I have sent the issues back to Apple. Thinking positive thoughts, thinking positive thoughts!

I'm hoping to see a release from 'Affinity Serif', the have announced a DAM product to be released soon. They have done sterling work with Affinity Photo & Affinity Designer.

thank you very much for this help. I will give it a try!

You're not alone here, especially when you consider the emphasis Apple is putting into the camera capabilities of the iPhone 7 and touting "shot on an iPhone" in their ads. It's as if Apple is betting on "we'll do it all for you in the camera" as a photo strategy without considering the need for outside creative tools that are essential for professionals. It is especially laughable when Apple recently showed Lightroom being used to edit photos on an iPhone during the recent launch event. It is simply ridiculous to seriously consider editing a 12 megapixel image on a 4-5" screen. The demonstration was meaningless for both professionals and consumers alike. Professional work is done on the desktop with powerful tools. This is why it continues to be important to communicate complaints and suggestions to Apple directly.

FWIW I wrote up a compilation of known issues based on reviewing Leonie's posts:

http://tech.kateva.org/2016/07/aperture-in-el-capitan-not-showing.html

Great work! Thanks for the link.

One minor correction. You wrote "You can no longer order print products from Aperture (Yosemite too)"

It is worse than that. We cannot order print products anymore from Aperture at all, independent of any system version. Apple killed the Print Products Store support for Aperture completely. That was the final nail to the coffin.

I have plans to buy a Nikon DL24-500 camera when it comes out. It shoots Nikon .nef RAW. One of the other issues with continuing to use Aperture is that all Apple Raw updates will not work in Aperture as far as I know.

I purchased my current camera after Apple stopped the development for Aperture. But since the RAW support for new cameras is rnow eleased as updates to OS X and not to Aperture or iPhoto, Aperture can also use the RAW support.

I still can develop the RAW images in Aperture. It just requires to update to the most current macOS X.

I have the suspicion that Apple has been moving from a content/media creation focus, to a content/media consumption focus. I believe I need to look elsewhere for a reliable future using pro tools.

I have the same error, which I have also reported on:

I am using 27 inch iMac 2010.

I have just installed Sierra Release version 10.12. With Aperture 3.6, I am receiving this notification repeatedly and consistently:

Internal Error:

An uncaught exception was raised. Choose “Continue” to continue running in an inconsistent state. Choose “Crash” to halt the application and file a bug with the Crash Reporter…..

The error is raised when I seek to IMPORT images. However, if I ‘CONTINUE’ the images import.

The error is raised if I try to alter an EXPORT preset. I am unable to adjust the export preset. Fortunately I have many presets setup.

This is the advice on the Apple Support site for addressing this kind of issue.

Get help with Aperture 3

https://support.apple.com/en-us/HT201289

As per above, I have now (a) Repaired, then (b) Rebuilt the database. Same fault results, as below. Aperture seems to possess most functionality, however, I remain ANXIOUS that my version of Aperture is on its last legs!

The Crash Report details are:

Exception Name: NSInvalidArgumentException
Description: *** -[__NSArrayM insertObject:atIndex:]: object cannot be nil
User Info: (null)

0 CoreFoundation 0x00007fff8332f7bb __exceptionPreprocess + 171
1 libobjc.A.dylib 0x00007fff97a9ca2a objc_exception_throw + 48
2 CoreFoundation 0x00007fff8324b6ad -[__NSArrayM insertObject:atIndex:] + 1389
3 RedRock 0x00000001036d339c +[RKPropertyMgr customInfoKeys] + 308
4 RedRock 0x00000001036d3741 -[RKPropertyMgr dependentKeyPathsForKey:] + 795
5 RedRock 0x00000001036d3948 -[RKPropertyMgr dependentKeyPathsForKeys:] + 201
6 Aperture 0x0000000102d14817 Aperture + 1640471
7 Aperture 0x0000000102d157bb Aperture + 1644475
8 Aperture 0x0000000102edf040 Aperture + 3518528
9 Foundation 0x00007fff84d2dc88 __NSFireDelayedPerform + 417
10 CoreFoundation 0x00007fff832aff44 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 20
11 CoreFoundation 0x00007fff832afbd3 __CFRunLoopDoTimer + 1075
12 CoreFoundation 0x00007fff832af72a __CFRunLoopDoTimers + 298
13 CoreFoundation 0x00007fff832a72f1 __CFRunLoopRun + 2081
14 CoreFoundation 0x00007fff832a6874 CFRunLoopRunSpecific + 420
15 HIToolbox 0x00007fff82846f6c RunCurrentEventLoopInMode + 240
16 HIToolbox 0x00007fff82846da1 ReceiveNextEventCommon + 432
17 HIToolbox 0x00007fff82846bd6 _BlockUntilNextEventMatchingListInModeWithFilter + 71
18 AppKit 0x00007fff80f3d5f5 _DPSNextEvent + 1093
19 AppKit 0x00007fff8164d8eb -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1637
20 Aperture 0x0000000102ff0a81 Aperture + 4639361
21 AppKit 0x00007fff80f31fbd -[NSApplication run] + 926
22 ProKit 0x00000001043e339a NSProApplicationMain + 333
23 Aperture 0x0000000102b940b4 Aperture + 65716
24 Aperture 0x0000000102b93a44 Aperture + 64068