By the way, I also verified the app with spctl, and it checks out:

Last login: Tue Jul 28 09:51:10 on ttys000
Grahams-iMac:~ grahamcox$ spctl -a -v /Users/grahamcox/Projects/Mapdiva\ Built\ 
Apps/Artboard_1.9.8_NS_GM3.app 
/Users/grahamcox/Projects/Mapdiva Built Apps/Artboard_1.9.8_NS_GM3.app: accepted
source=Developer ID




What could cause Gatekeeper to fail only for some users? Does it phone home? 
Could this just be a connectivity/Apple issue?

—Graham

> Hi all,
> 
> I’m having an issue with codesigning a version of one of our Mac apps with a 
> Developer ID. It all seems to go perfectly smoothly, but some of our users 
> (and some in-house testing) have reported that the app does not launch - it 
> just bounces in the dock forever UNLESS the system is set to accept apps from 
> anywhere.
> 
> We thought this was isolated to 10.10 but apparently we have a report with 
> 10.9 also.
> 
> This is logged when launch fails:
> 
> 7/27/15 8:40:55.108 PM com.apple.xpc.launchd[1]: 
> (com.apple.xpc.launchd.oneshot.0x1000000e.Artboard[8344]) Service exited due 
> to signal: Terminated: 15
> 
> 
> I’m using Xcode 6.3 and I’m signing by using the “Export application” option 
> from the Archive Organiser. I select “Export a developer ID-signed 
> application” and I am offered a single signing identity which is our 
> company’s ID. The app is exported with no reported errors and launches just 
> fine on the two machines I own, which cover both 10.10 and 10.9 OS versions. 
> All our signing resources are up to date.
> 
> I’m at a bit of a loss as to what the problem is and how to fix it.
> 
> Can anyone give me a shove in the right direction?
> 
> —Graham


_______________________________________________

Cocoa-dev mailing list ([email protected])

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to