Does aperture work with Sierra

I'm running Sierra on a mid/late 2011 MacBook Pro 13" with upgraded SSD drive and 16GB (yes, 16) RAM. It launches, I can import, I can edit, I can export. I'm not using this setup for my daily/weekly Aperture work, though. For that work, I use a late 2012 iMac 24" with 3TB fusion drive and 16GB RAM. Here, I am at El Capitan and have been reluctant to upgrade, having made it through Yosemite and El Capitan since Aperture's poorly executed demise by Apple.

Basically the same as on El Capitan. The same glitches as previously. It launches and we can edit, but some tools are behaving in unexpected way. A few users are reporting, that Aperture is now crashing in Full Screen Mode.

I cannot reproduce this issue, it might be platform dependent.

See this discussion: Re: Will Aperture 3.6 work in Mac OS Sierra?

Works with no problems on my MacPro (late 2013) under macOS Sierra

Aperture is operational here on two iMacs running Sierra. Pleasant surprise.

I have had no serious glitches in my use of Aperture 3.6.

I have had more trouble today with my Scanner but persevered and got it going.

Has anyone tried Aperture on a Macbook pro with Sierra

I have Aperture running on two MacBook Pro (Retina, 15-inch, Mid 2015).

It is working in Full Screen mode as before without rashes.

Aperture is not working for me. It opens fine, but if I try to actually do something, crash. Disappointment! I've tried reinstalling, but no luck. If I have to install an older system on a separate disk, I will… But I remain hopeful, since it does seem to be working for most of you. Perhaps an update will fix this. I have a 2012 iMac.

Aperture running with Sierra on my MBP, albeit a little slow, especially getting Aperture to open. My MBP only has 4GB RAM and is noticeably slower than the iMacs but Aperture does work.

I fixed the problem. The Aperture sign "multiple crashing is bad" showed itself, reminding me that the program has built-in repair modes. The third, and final, did it for me. Sounds strange, but rebuilding the library did the trick! I did wonder if perhaps there was some background update from Apple, but no, I have two libraries, and the second one crashed as well until rebuilt. So, I presume Sierra didn't like something in those libraries! If you're having issues, you should try this.

Now, I might add, Aperture seems very quick and smooth. Of course, I have yet to test it properly. Whew!

I have a late 2013 iMac i7 with 32GB of RAM and 3TB fusion drive. I have not yet upgraded to Sierra, but still have a significant Aperture 3.6 library that I have not yet migrated to Apple Photos (which I like a lot for the iCloud library management across all my devices). Aperture 3.6 has been flawless for me on El Capitan. Any thoughts/perspective on whether my configuration is lower risk for problems if I move to Sierra

Given reports of problems and time spend rebuilding libraries, I'm leaning to stay on El Capitan and just made a big push so get the rest of my library over to Photos in the next few months.

Thoughts, perspectives, suggestions welcome . . .

I only have 2015 Mac models in use with Sierra. My Macs have 16GB RAM. And I can launch Aperture, edit, and export from Aperture.

I cannot say anything about the 2013 models, if there are unexpected problems, but your Mac looks powerful enough to support any image processing application. My older MacBook Pro's 2011 worked well with Yosemite, but never supported El Capitan well. I retired them.

The Photos.app on Sierra has improved a bit. The Places maps are now more detailed, because they have a satellite view in addition to the street maps. we can search for HDR photos using smart albums. The search is less buggy.

I love the ability to transfer text and other items between my devices by copy and paste on Sierra. The shared clipboard is great.

Thank you leonie! Very helpful.

Just for information, my older 27" iMac is late 2012, with 3TB Fusion Drive and 16GB RAM. Aperture is working fine with Sierra on this iMac.

On my Early 2013 Retina Macbook Pro it seems to be working fine. On my Late 2009 iMac, it crashes every time I try to maximize a window or otherwise enter full screen mode.