I got this error message while running my app from within Xcode and the Archived exported app do NOT execute under macOS 10.14
[default] Unable to load Info.
Apps linked against 10.14 (Mojave) need to add this key to their Info.plist
NSAppleEventsUsageDescription
Details on usage available here Apple Developer Video and here Apple Developer Forum.
I have the same problem with my project - everything builds fine, but nothing show up except that error:
Unable to load Info.plist exceptions (eGPUOverrides)
It IS Mojave bug. Apple trying to fix this issue in the next versions of Xcode. For now, I recommend to just downgrade the IDE for 9.4.1 version and waiting for resolve. It was the only option worked for me.
I've got xcode 10.1 and mojave 10.14 and solve it by build to Legacy Build System
(as you mentioned) but also when my app ran, it triggered the OS to open an accessibility window for that app. I removed the current app association with -
and re-added it.
This seems to be resolved with the Public release of 10.14.4. I was having the issue until yesterday using 10.14.3 Public release but after overnight update the issue is gone.
I have removed the various work around suggestions such as 'Build System Legacy' in XCode and NSAppleEventsUsageDescription, which didn't actually help in my case, and everything is still fine.
Possibly not relevant but I had a similar issue today - XCode 10 + High Sierra.
Mine was an issue with the Fabric/Run script in the Build Phases window. The error suggested it was a 'timing' issue. I checked the box that said 'Run script only when installing' in the build phases window, and now my project builds and runs again.
[UPDATE] My solution was found here: XCode 10 archive failure
It's not an Xcode bug, it's a Mojave bug.
I met this error every seconds. No matter I open any app, all comes with this bug in the Console.
I can't use the settings in System Prefrences - Security - Privacy - Accessibility
because I can't add anything to the list ( I'm sure I unlocked the panel )
And when I start Steam, it also cause this error ------ Then the Steam exits on it's own.
Seems it was due to the CoreServices
or LaunchServices
, but I don't know what to do.