Aperture requests access to Contacts

jwang611
New Contributor

Hello all,

I'm currently creating software packages for Aperture and noticed the same issue I was having with Final Cut Studio 3. When I open the application on a new account, it asks to access your Contacts. While building the package with Composer, I answered yes to this prompt, but this setting did not carry over to the new machine (and new accounts) that I deployed the package too. Has anyone else experienced this and know a way to stop it from asking?

EDIT: It occurs to me to let you all know we're running these on Mountain Lion.

Thanks!

1 ACCEPTED SOLUTION

seanmbrage
New Contributor

I know this is one of the new 10.8 features, with iOS-style app-specific permissions for things like Contacts. This is a user-specific and not system-specific setting so I don't think it's currently stoppable. It'd be nice to be able to set "do not prompt" for this.

View solution in original post

4 REPLIES 4

seanmbrage
New Contributor

I know this is one of the new 10.8 features, with iOS-style app-specific permissions for things like Contacts. This is a user-specific and not system-specific setting so I don't think it's currently stoppable. It'd be nice to be able to set "do not prompt" for this.

jwang611
New Contributor

Thanks for the info! I'll test it on 10.7 to see if this happens.

CasperSally
Valued Contributor II

This 10.8 'request to access contacts' prompt sure is annoying as it doesn't always come up the first time you launch an app. Twice now I've packaged apps and then when testing on the 2nd or 3rd launch I'm seeing the prompt as a user. Our students don't need to see the prompt, sure would be nice if there was a setting to never allow access to contacts with any app.

JPDyson
Valued Contributor

I remember seeing this on the 1Password message boards.

http://support.agilebits.com/discussions/questions/4335-does-1password-need-access-to-contacts

It's a virtual certainty that if the app supports sending email bug or crash reports, you'll get this prompt. The real problems are that it seems we can't preemptively approve an app, and the app can't give more details as to why this is happening.