Q: Will Aperture 3.6 work in Mac OS Sierra?

While Aperture is not part of macOS, I don't think we're going to get much traction from filing bug reports for it specifically, since it's no longer officially supported. I think we'll get more attention if we file bug reports under macOS since that's where a lot of Apple's attention is currently focused.

Aperture's exception crashes with older Macs suggest Sierra video driver bugs. These are things Apple might be interested in fixing, so definitely report them as Sierra issues. Apple isn't going to touch Aperture's source code.

I've seen some reports of FCPX crashes post Sierra. I don't know of course, but if Aperture works well on post-2010 Macs that would fit with driver bugs.

Prior to final release Sierra release notes were said to reference Aperture issues. The current release notes don't list any: https://developer.apple.com/library/content/releasenotes/MacOSX/WhatsNewInOSX/Ar ticles/OSXv10.html#//apple_ref/doc/uid/TP40017145-SW1

Which does fit with Brian O'Reilly's test results...

Prior to final release Sierra release notes were said to reference Aperture issues. The current release notes don't list any

I've yet to see any reports of Aperture working bug-free on any version of Sierra running on older Macs such as the Late 2009 iMac. This includes the latest beta, released today.

Using the latest macOS release: 10.12.1 (16B2548a):

1) The crash no longer appears to occur when switching to the Info tab while viewing a photo.

2) The application can be switched to full screen mode by tapping the F key. However when toggling back out of full screen mode by tapping the F key again, the application crashes/closes with no error messages displayed.

It didn't work on my real library. But I just realized that some of those photos were referenced and offline so probably they wouldn't get regenerated. So will try again tonight with all referenced files online.

I don't think this has anything to do with referenced libraries since I'm affected and using a managed library. The bug appears specific to older hardware, not to any particular Aperture installation settings or library configuration.

Not specific to referenced libraries, but one of my test libraries with only 1 photo that caused the crash was fixed by updating previews. This fix didn't work for my main library, but it could be because it couldn't regenerate all the previews on photos that were referenced and offline.

that would fit with driver bugs.

You may be on to something. I've discovered a similar issue with Little Snitch. When attempting to resize or maximize the "Rules" application window, it crashes as well.

However, the fact that just about every other application works just fine when resizing or maximizing windows suggests to me that this bug relates to some older code used by some apps (including Little Snitch and Aperture) relating to window sizing. That older code, in turn, may or may not relate to video drivers. But the point is that since it's application specific, the fix should be as well without requiring new video drivers.

What computer model/year are you running this on?

MacBook Pro (Retina, 15-inch, Late 2013)

2.3 GHz Intel Core i7

16 GB 1600 MHz DDR3

NVIDIA GeForce GT 750M 2048 MB

Intel Iris Pro 1536 MB

I suspect you are encountering an unrelated issue, as others with newer models such as yours have not encountered the problem. I have an Early 2013 rMBP and I haven't encountered any Aperture issues with it at all. For me, the problems only occur on my Late 2009 iMac.

Perhaps the problem is with specific chipsets? yours has an integrated graphics processor, mine an NVIDIA.

yours has an integrated graphics processor

Helll* no.

*It's ridiculous Apple censors this word.

was referring to your early 2013 MacBook pro which doesn't have a problem (CIIR, based on google search your model has an integrated HD 4000 graphics). So maybe the problems are with certain non-integrated chipsets. All just speculation until we get a bigger sample size of working and non working configurations.

My Early 2013 rMBP has both Intel integrated graphics as well as an Nvidia GForce dedicated GPU, switching automatically as needed.

Anything's possible, but to me the evidence is pointing to older Macs and only two applications I'm aware of: Aperture and Little Snitch. None of these issues appeared before Sierra, and given that Little Snitch isn't exactly a graphics intensive app, I still suspect it relates to some system call used by both apps which has been deprecated by Apple.

For example, Apple's Sierra documentation states that "the UIAutomation framework is deprecated". I'm not sure what that framework was used for, but if it related in any way to drawing, organizing, or resizing application windows, then any older apps still using it might crash under Sierra. Then again, if that were the case it should impact all systems rather than just the older ones. So perhaps it's a combination of some deprecated functions combined with specific older hardware.

I've sent a bug report to the makers of Little Snitch in the hope they can fix it as well as shed some light on the underlying cause which might also relate to Aperture.