So, Growl.framework 1.3+ uses networking to communicate with growl when in a sandboxed app, either if the app itself has the network client entitlement or via an XPC which we provide that can be renamed and resigned for use in your app. For more information on all this, see here http://growl.info/documentation/developer/implementing-growl.php#sandboxinginyourapp
You can hop in IRC to #growl on irc.freenode.net if you have any questions on the process, compatibility, and so forth. Also, we maintain a developer oriented list that we are less likely to lose an important thread in here: http://groups.google.com/group/growl-development On Jun 27, 2:49 pm, Stephen Lind <[email protected]> wrote: > Hi Growl users, > > I submitted an update to my app to the Mac App Store, but my entitlements > were rejected: > > -- > We've determined that one or more temporary entitlement exceptions > requested for this app are not appropriate and will not be granted: > > com.apple.security.temporary-exception.apple-events: > com.Growl.GrowlHelperApp > com.apple.security.temporary-exception.mach-lookup.global-name: > GrowlApplicationBridgePathway > -- > > Without these entitlements, Growl (I'm on 1.22) will not function in the > Sandbox. > > On this > thread<http://lembacon.com/2011/07/use-growl-inside-lions-sandbox/#comment-1371>, > I noticed that the Growl 1.3+ Framework uses different sandbox > entitlements. Has anyone successfully gotten a Sandboxed app with Growl on > 1.3+ working and submitted to the app store (after June 1, 2012, when > Sandboxing became enforced) -- You received this message because you are subscribed to the Google Groups "Growl Discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/growldiscuss?hl=en.
