Cannot find executable for CFBundle CertUIFramework.axbundle

XcodeXcode5Xcode6

Xcode Problem Overview


Just updated to Xcode 5 and this is the first error its throwing on the logger for all my apps. Can't seem to understand why this is happening.

    2013-09-19 10:46:54.341 MyApp[1156:a0b] Cannot find executable 
for CFBundle 0x8a7c7a0 </Applications/Xcode.app/Contents/Developer/Platforms/
iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator7.0.sdk/
System/Library/AccessibilityBundles/CertUIFramework.axbundle> (not loaded)

Edit (11-11-2013): To everyone reading, once I waiting for a solid working solution to accept and close. The highest voted answer works until you re-open the project only.

Edit (30-09-2014): I can see this has been sorted since XCode 6 has been released! Finally

Xcode Solutions


Solution 1 - Xcode

Final Edit-

> Temporary workaround: click iOS Simulator > Reset Content and > Settings... and run again. > > This error message may reappear at random. For me, it happens when I > launch a different application. There are several threads in Apple dev > forums and in StackOverflow about this problem, but none have a > definitive answer. This seems to be a SDK error to be fixed in the > next Xcode version. > > Updated: October 3.

CREDIT - Please check this answer - https://stackoverflow.com/questions/18036381/xcode-5-error-certuiframework-axbundle?rq=1

Further Edit
Although this was potentially the issue resolution at the time. I believe some of the newer answers below relating to the better touch tool are in fact the correct resolutions.

Solution 2 - Xcode

After reading Kirill's answer I did some digging as I didn't want to disable BetterTouchTool for everything just the "iOS Simulator" and you can. Open the "iOS Simulator" and will it as the active app go to the BTT drop-down menu from the top bar (of that screen if you have more than one) and select "Disable BTT for Current App". It will turn to a play icon when it's disabled. Make sure the app name on the bar is still "iOS Simulator" as mine jumped to "Finder" a few times when I clicked the top bar!

BTT disabled for current app

Now re-set the simulator (if it doesn't work) and rebuild. You shouldn't get the error! :) Don't forget to clear the error if it's still there. ;)

BTT seems to remember what apps it's disabled for (or at least it does when you close and re-open the app that's disabled I haven't tried a system re-boot yet).

Solution 3 - Xcode

Its easy. Go iOS simulator and reset content and setting.

enter image description here

Thanks

Solution 4 - Xcode

If you are using XCode-5 then just reset the simulator "Reset Content and Settings" and run once again

Solution 5 - Xcode

So I was having this error too in Xcode 5 and 5.1. I wanted to figure out if it's Xcode bug or something else, so I did a fresh install of Mavericks 10.9.2 and Xcode 5.1. Everything seemed fine after multiple tests.

Here is where the problem began. I put the apps and settings that I mostly use and the error came back. So I deleted everything and started adding everything one by one. After couple days I had bingo! The problem is with BetterSnapTool and BetterTouchTool

Update 12.12.2014

Just started using Xcode 6.1 and noticed that this bug seems to be gone at least with Xcode 6.1 simulators and BTT 0.9985 versions.

Update: As GasB pointed out, it is possible to disable BTT for certain apps. So just disable it for iOS Simulator. You just have to remember not to use gestures while using the simulator as that triggers the error message.

Simple solution:

Remove the ticks in preference pane, reset simulator and do clean build. The error message will disappear. No control for the apps.

Solution 6 - Xcode

I had the same problem and solved it setting the 'Localization native development region' to match my systems region. In my case from 'en' to 'de'. The referenced files are stored in localized versions in your filesystem. So this setting is used to identify the needed version.

You can find that setting in your project settings at 'Info' -> 'Custom iOS Target Properties'.

Solution 7 - Xcode

Resetting the simulator ‘fixes’ it because it turns the accessibility support off. You can normally achieve the same by simply disabling the ‘Accessibility Inspector’ in the ‘Settings’ app.

If, however, you need it enabled, particularly hate this error message, and are feeling adventurous then you can use the following monkey patches to silence the error: https://gist.github.com/alloy/9277316. (Be sure to NOT include this in your release builds.)

Solution 8 - Xcode

Resetting the simulator is a PITA, I found a way to get rid of these messages without having to to this:

  • go to Settings > Accessibility
  • turn on Accessibility Inspector
  • turn off Accessibility Inspector
  • quit Simulator

Solution 9 - Xcode

I had this problem with Xcode 5 in ML 10.8.5

I re-installed Mountain Lion (in a Parallels' VM), then update ML to 10.8.5.

Then installrd Xcode 5, and it's worked fine.

I think that the error is caused by a third SW installed in ML.

Solution 10 - Xcode

The application Moom is also causing this issue, and I couldn't find a way to disable it for just the iOS Simulator. So for now I disabled it's accessibility features.

Solution 11 - Xcode

I'm on Mavericks (10.9.3) and encountered the same error in xCode(5.1.1).

I tried anything - reinstalling xCode from both AppStore and dmg. Resetting the emulator resulted in the same error and deleting the Simulator SDK folder gave no results too.

The issue on my end was indeed Moom as mentioned by @aorcsik! Disabling it's accessibility, followed by clean (cmd+shift+k) in xCode cleared the error.

Solution 12 - Xcode

  1. Open Disk Utility and apply Repair Disk Permissions in Macintosh HD.
  2. After doing above step, apply Reset Contents and Settings in iOS Simulator.

This above solution can definitely fix your problem.

Solution 13 - Xcode

I had this problem, and none of the answers in this thread could fix it. Mine was simple UI with a UIDatePicker. I resolved it by removing the UIDatePicker and the associated code, then added them in again. Problem solved!

Solution 14 - Xcode

For me it was Keyboard Maestro, adding the simulator to Maestro's exclude list silenced the warnings

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestioncarbonrView Question on Stackoverflow
Solution 1 - XcodeStuartMView Answer on Stackoverflow
Solution 2 - XcodeGazBView Answer on Stackoverflow
Solution 3 - XcodeTunvir Rahman TusherView Answer on Stackoverflow
Solution 4 - XcodeNagarajView Answer on Stackoverflow
Solution 5 - XcodePahnevView Answer on Stackoverflow
Solution 6 - XcodeMichaelOView Answer on Stackoverflow
Solution 7 - XcodealloyView Answer on Stackoverflow
Solution 8 - XcodeGereonView Answer on Stackoverflow
Solution 9 - Xcodeuser2892348View Answer on Stackoverflow
Solution 10 - XcodeaorcsikView Answer on Stackoverflow
Solution 11 - XcodeMartin VelchevskiView Answer on Stackoverflow
Solution 12 - XcodefloydddView Answer on Stackoverflow
Solution 13 - XcodeReturn_Of_The_ArchonsView Answer on Stackoverflow
Solution 14 - XcodeFjölnirView Answer on Stackoverflow