Will Aperture 3.6 work in Mac OS Sierra?

The weird thing is that I exported the project that I last imported as a new library, then deleted that project from the mail library. I then opened up the exported library and showing an image in fullscreen also crashes there. So I thought that there must have been something specific to that project, so I opened up the original library that no longer contained that project and it still crashes! So the original library crashes, and the exported one crashes, but a brand new library with only a couple of images doesn't crash. For the record the exported library is only 10 or so images.

There are no previews being generated in both cases. And it only crashes when I press F to show (any) image in full screen, otherwise things work fine.

I've issues with Aperture with the newly released Mac OS Sierra.

The application crashes when switching to 'F' full screen. Also when using 'W' to switch between the tabs. I have forwarded a crash report, from the pop up dialogue window in Aperture.

"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 crash reporter. Choosing 'Crash' will result in the loss of all unsaved data."

I will try again later...

I was using a MacBook 11" 2014 (maxed). I won't be updating the OS on my MacPro until I find out what's happening with Aperture.

.... just to add

There is only a handful of images on my MacBook Air / Aperture (80 approx). I only use my MacBook Air to offload images from my cameras 'in the field' so that I may start culling & key wording before transferring the projects to the MacPro at base where the heavy lifting is done.

The Loupe appears to be a little 'sticky'.

I've tried going to 'Full screen' using the Menu & avoiding the 'F' key.... still an issue. The 'Internal Error' will appear. If you choose 'Continue' Aperture will behave as normal..... until you get the 'Internal Error' again when tabbing the windows. Aperture will eventually lock up, which then requires a 'Force Quit'.

Some images appear now with "Unsupported File Format', after closer inspection these are images which are being sync'd with SmugMug.

No doubt there are more issues with Aperture, I thought it best to get some feedback back to the Aperture community at this early stage.

So looks like you have the exact same problem as me (see posts just above yours). At least I'm not the only one. Sigh...

I've not yet completely convinced myself, but it looks like the previous problem with brushing when a Burn or Dodge adjustment is present on an image may, in fact, be gone. This would be remarkably good news, indicative of a problem within El Capitan and not Aperture! I'll have to notch out some time to do side-by-side tests with Aperture under Sierra and El Capitan to verify, but it would be a very welcome relief to no longer have to ping pong my process between two versions of the OS.

Are we building an extensive list anywhere of known differences between Yosemite, El Capitan, and Sierra?

There is (already !) a new Siera beta released today... Its probably sound to wait a few weeks before updating for us Aperture lovers...

Are we building an extensive list anywhere of known differences between Yosemite, El Capitan, and Sierra?

You could start a discussion to collect the known problems 🙂

Seems it's not about any specific photo going into full screen that causes the crash. I can just have a project view open and go into full screen and it will crash. It will also crash when trying to open Metadata presets, and the Inspector HUB. But again it only happens in my main library, and the one I created by exporting a small project. A brand new library with a couple of images does not have this issue.

Proggie wrote:

Seems it's not about any specific photo going into full screen that causes the crash. I can just have a project view open and go into full screen and it will crash. It will also crash when trying to open Metadata presets, and the Inspector HUB. But again it only happens in my main library, and the one I created by exporting a small project. A brand new library with a couple of images does not have this issue.

Then you may have corrupted media files in the library or the library needs fixing.

Corrupted media files can be prevented from being processed by launching aperture with Shift key held down during the launch. That will defer the generation of previews. Did this test have any results?

Did you try to repair or rebuild the library?

Holding shift on launch doesn't help (no previews to generate anyway). And I did repair permissions and rebuild a couple of times and didn't help either.

And another user above has exactly the same problem, so it seems it may have something to do with Sierra (and perhaps 2014 and older laptops) after all.

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 and upon reboot "error in library" window shows up. Upon trying to rebuild permissions now on library, the progress bar hasn't even shown up. So total meltdown! BAD NEWS for Aperture!!! BOOO HISSS APPLE FOR DROPPING APERTURE!!!! PHOTOS IS A JOKE!

Yup you are the 3rd person (including me) who's experienced this. What machine do you have? One person says that it works for them but they have a 2015+ MacBook Pro where as I have a late 2013 and the other person has a MacBook 2014.

Aperture remembers when you are in full screen mode so if you relaunch it, it will continue to crash. So you could start it up with a brand new library, which for me doesn't crash in full screen mode, and then disable full screen mode. Then if you start up your original library it won't crash on launch anymore. But it will continue to crash when you go into full screen mode again. For me it also crashes when opening Metadata profiles and displaying the Inspector HUB.

I'm going to file a report once I get a new beta of Sierra, and hopefully it will get fixed. But I think I'm going to start preparing for a migration to Lightroom.

Anyone successfully using Aperture with Sierra with a MacBook Pro (Retina, Mid 2012)?

Partially only...

If you want to get data info, or choose full screen, or edit any file, forget about it.

Now we can say: Aperture is really dead!.

I am deeply disappointed.

Sad but true, a powerful tool like this, being thrown in the trash.

I would hope for some miracle, to bright those people minds, but miracles don't exist...

Sierra Cronicals Continue: Yep so after complete rebuild of library it opened , but AGAIN gives the "error in library" message as soon as it opened. At least I am able to open the program now and edit files seems , so far ..... ok. Clearly "F" key is off limits as it will melt down aperture. Also "w" key for tab switches. Don't touch it! It really really annoys me apple has gone down this road. Ticking off it most loyal die-hard pro customers who only want to use Apple's very own great Aperture program. Neither Capture One nor Lightroom are nearly as intuitive nor efficient as Aperture despite that C1 is more powerful. And to offer "Photos" as an alternative...thats a joke and perhaps the worst photo program out there. So quite devastated by apple's uncaring policy. To have hundreds of billions in the bank at home and abroad and chose not to maintain a single simple program with a loyal top price hardware buying customer base?!!! Really Apple!!@#? Like a weeks worth of coder patch time to ensure compatibility is going to bankrupt you? Thats ridiculous and having owned apples since the company existed year 1, I can only say what a shame. Shame on apple for dropping the ball on both Final Cut and Aperture! Someone with coding experience Please PLEASE work some magic and deliver us a patch to keep this boat afloat!