NSWorkspace launchApplication and gatekeeper
NSWorkspace launchApplication and gatekeeper
- Subject: NSWorkspace launchApplication and gatekeeper
- From: Totte Alm <email@hidden>
- Date: Thu, 09 Jan 2014 13:27:08 +0100
Hello,
I'm moving an older but large inhouse application from 10.6/32-bit/GC to 10.9/64-bit/ARC.
It uses an internal auto update functionally where the app can store itself into the database when it detects it is a new version, then the other users will get "update reminders" to download the latest version, which self updates.
Now, the tricky part on 10.9
I move "myself" to trash as theapp-old.app, unzips the fetched zipfile into /Applications (or where the user put it), all this works. The application is signed with a dev-id.
Then I use [NSWorkspace defaultWorkspace] launchApplication:pathstring] to launch the new copy.
[NSWorkspace defaultWorkspace] launchApplication:pathstring] returns YES (which means the app is launched or running), but the new instance isn't started and I get this in the log which sounds very much like "gatekeeper interference".
2014-01-09 13:11:33,981 launchservicesd[58]: Application App:"xxxxx" asn:0x0-563563 pid:2239 refs=7 @ 0x7fb00940b730 tried to be brought forward, but isn't in fPermittedFrontApps ( ( "LSApplication:0x0-0x564564 pid=2247 "SecurityAgent"")), so denying. : LASSession.cp #1481 SetFrontApplication() q=LSSession 100005/0x186a5 queue
2014-01-09 13:11:33,982 WindowServer[102]: [cps/setfront] Failed setting the front application to xxxxx, psn 0x0-0x563563, securitySessionID=0x186a5, err=-13066
If I manually (in Finder) launch the application it works fine.
Anyone has a Ptr to what I'm missing here?
/Totte
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden