-
All replies
-
Helpful answers
-
Sep 25, 2016 6:31 PM in response to benji888by freediverx01,states I must be a registered developer to report bugs there.
How-To: Create a free Apple developer account
https://9to5mac.com/2016/03/27/how-to-create-free-apple-developer-account-sidelo ad-apps/
-
Sep 25, 2016 10:51 PM in response to freediverx01by léonie,This User Tip explains how to use the developer bug reporter: https://discussions.apple.com/docs/DOC-7641
After reporting there we will at least receive some kind of reply.
-
Sep 27, 2016 10:46 PM in response to Nikontravelerby agoodmanwa,Caution!
My Mac Book Pro, early 2011, 15 inch, with maximum RAM has issues that cannot be resolved with a database rebuild and I plan to downgrade back to el Capitan.
Issues I found so far are both full screen (F) and info, result in "The Internal Error" dialogue box.
-
Sep 27, 2016 11:16 PM in response to Nikontravelerby agoodmanwa,And the only way to get back to work is to hit "Crash" in the dialog box, to close Aperture and than open it again.
-
Sep 28, 2016 6:06 AM in response to agoodmanwaby freediverx01,File a bug report. If you're on the beta or seed program, use Feedback Assistant.
It's good to know others are having this exact issue, so it's not an isolated case. But everyone needs to report this to Apple to make sure it gets fixed. The more people report this bug, they higher it will be prioritized by Apple's developers. The squeaky wheel gets the oil.
-
-
Sep 28, 2016 6:27 AM in response to agoodmanwaby léonie,Issues I found so far are both full screen (F) and info, result in "The Internal Error" dialogue box.
I had the "The Internal Error" only happen in the early Beta versions of Sierra, not in the current stable release. Are you still running a Beta version?
-
Sep 28, 2016 7:05 AM in response to léonieby freediverx01,I've reproduced the issue on the last beta, the GM, and the recently released beta.
I have a similar issue on the same computer when resizing a window in Little Snitch.
Which Mac do you own? For me this only occurs on my Late 2009 iMac but not on my Early 2013 rMBP.
-
Sep 28, 2016 7:32 AM in response to freediverx01by léonie,I have not yet upgraded the MacBook Pro late 2011 to Sierra, but Aperture is working on both MacBook Pros (Retina, 15-inch, Mid 2015) with the official Sierra release, also on my iMac 27", late 2013.
-
Sep 28, 2016 7:36 AM in response to Brian O'Reillyby agherrera,In response to Brian O'Reilly, AG Herrera is on a late 2014 iMac 4ghz i7 32gb RAM, Radeon M295R9 4mb
-
Sep 28, 2016 9:49 AM in response to freediverx01by Proggie,Curious what category you file the bug under via Feedback Assistant. I filed it under 3rd Party Apps since Aperture is not listed as one of the Apple apps. I wish you could update your own submitted bug for each new beta instead of having to file a brand new one each time. Still crashes for me on 10.12.1 Beta 2
-
Sep 28, 2016 10:23 PM in response to freediverx01by agoodmanwa,How does a "regular" user file a report?
-
-
Sep 28, 2016 11:20 PM in response to agoodmanwaby léonie,How does a "regular" user file a report?
There is a feedback link built right into Aperture - you can use the command "Aperture > Provide Aperture Feedback "
Or sign up for a free developer account. That will give you access to the bug reporter.
See this User Tip: Detailed and Effective Bug Reporting | Apple Support Communities
The Bug Reporter lets you describe the problem in detail and add attachments like screenshots or log files.
-
Sep 28, 2016 11:21 PM in response to léonieby freediverx01,Aperture is no longer officially supported so I don't recommend filing bug reports for Aperture itself. Instead, file the bug for macOS, and include the relevant details within.

