I’m not 100% sure if it’s related, but one user sent this to me which appeared
to coincide with the launch failure:
7/28/15 4:41:01.467 PM CoreServicesUIAgent[8607]: Error -60005 creating
authorization
7/28/15 4:41:11.624 PM CoreServicesUIAgent[8607]: An uncaught exception was
raised
7/28/15 4:41:11.624 PM CoreServicesUIAgent[8607]: *** -[NSFileManager
fileSystemRepresentationWithPath:]: nil or empty path argument
7/28/15 4:41:11.624 PM CoreServicesUIAgent[8607]: (
0 CoreFoundation 0x00007fff928e303c
__exceptionPreprocess + 172
1 libobjc.A.dylib 0x00007fff966e576e
objc_exception_throw + 43
2 CoreFoundation 0x00007fff928e2eed
+[NSException raise:format:] + 205
3 Foundation 0x00007fff901cf29b
-[NSFileManager fileSystemRepresentationWithPath:] + 122
4 XprotectFramework 0x00007fff8d673fbf
-[XProtectDylibCheck parseExececutableAndLoaderPaths:] + 329
5 XprotectFramework 0x00007fff8d673cec
-[XProtectDylibCheck parseLoadCommands] + 898
6 XprotectFramework 0x00007fff8d67440d
-[XProtectDylibCheck parseMacho] + 1050
7 XprotectFramework 0x00007fff8d67763d
+[WorkerThreadClass performDylibBundleCheck:] + 602
8 XprotectFramework 0x00007fff8d678b53
+[WorkerThreadClass threadEntry:] + 4910
9 Foundation 0x00007fff90202dc2
__NSThread__main__ + 1345
10 libsystem_pthread.dylib 0x00007fff8e6a9268
_pthread_body + 131
11 libsystem_pthread.dylib 0x00007fff8e6a91e5
_pthread_body + 0
12 libsystem_pthread.dylib 0x00007fff8e6a741d thread_start
+ 13
)
7/28/15 4:41:11.624 PM CoreServicesUIAgent[8607]: *** Terminating app due to
uncaught exception 'NSInvalidArgumentException', reason: '*** -[NSFileManager
fileSystemRepresentationWithPath:]: nil or empty path argument'
This could suggest that there’s some internal path that’s gone astray that
could be preventing the launch. What’s a bit odd though is that it only affects
some users - I would have expected that if there were an issue here it would
affect all users including me when I’m testing.
The app links to an internal framework (actually several) so I’m wondering if
it’s related to that, since the faling call is
-parseExececutableAndLoaderPaths: (which is apparently some internal
typo-ridden API). However I’ve checked and double-checked the build settings
and it all seems fine - the runtime search paths include
@executeable_path/../Frameworks, the Frameworks themselves are copied into the
build and it all works fine for me.
I’m really grasping at straws, can anyone think of anything else I can check?
—Graham
> On 28 Jul 2015, at 12:08 pm, Graham Cox <[email protected]> wrote:
>
> 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
_______________________________________________
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]
