On Oct 12, 2014, at 12:32 PM, Kyle Sluder <[email protected]> wrote: > Curious: have you tried scouring your machine for all copies of the app and > deleting them? Since it’s generally not possible to associate a running > executable with a file on disk, the OS might be trying to look up your app > via bundle identifier and finding an old, stale copy whose code really > doesn’t match what’s running.
I'm usually pretty good at avoiding this problem, but I double-checked and found four other copies on different attached startup disks (Lion, Mountain Lion, Maviericks and Yosemite main Applications folder). So I removed all of those and tried again, and -- same failure. >> Is code signing now making it impossible to use shared frameworks at all, >> going forward? That would be a huge change to spring on the developer >> community without advance warning. > > What do you mean “shared frameworks”? As in, frameworks that live outside of > your app wrapper? Because frameworks in and of themselves are certainly still > usable. I mean a framework placed in /Library/Frameworks with the proper Run Path Search Paths and other build settings so it can be used by multiple applications. -- Bill Cheeseman - [email protected] _______________________________________________ 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]
