Geek Answers Handbook

Xcode 7.1: Simulator could not be opened because the developer id could not be confirmed

I upgraded my Mac OS X to 10.11.1 El Capitan. When I try to run the application on Xcode 7.1, I get a message that the message “Simulator” could not be opened, because the developer ID could not be confirmed. See screenshot.

Why is this message? I can not test any application on Xcode 7.1.

Screenshot for error

+6
source share
5 answers

Apple believes that security is that you can only open applications that you have downloaded from the App Store.

Well, to open any application that you have downloaded and installed from anywhere, you need to allow permission. For this:

  • Open 'System Preferences'
  • Go to the "Security and Privacy" section and click on the "General" tab.
  • Click on the “Lock” icon, which you can find on the lower left screen and enter the administrator password.
  • The final step is to select “Anywhere” in the “Allow applications downloaded from:” section, and then click the “Lock” icon again.
  • What is it. Now you can run any application.

enter image description here

Enjoy it!

+11
source

Gatekeeper requires that all applications downloaded from the Internet be verified. Since you downloaded Simulator using Safari, you need to check it and add it to the list of accepted applications. Here is a quick way to do this:

  • Run Terminal.app
  • Type the following command sudo xattr -d com.apple.quarantine /Applications/Xcode.app/Contents/Developer/Applications/Simulator.app

I found the answer here .

+7
source

Simulator.app is distributed by Apple and must be properly encoded.

The dialog box that you see indicates that the version you did not pass checks for the correct key codes.

Possible reasons:

  • You made local changes to Xcode.app or Simulator.app to revoke the signing of Apple code.
  • A disk corruption or maybe a transport error caused some resources in Simulator.app to not be valid, so the signature is no longer valid.
  • You downloaded an unofficial copy of Xcode.app (or just Simulator.app), which was modified by a third party. Google "XcodeGhost" for information on why this is a bad idea.
  • The simulator.app you are trying to open is not really Xcode.
  • An error in Gatekeeper or OS X can lead to a false result.

Please also update your question using the following steps (assuming you have configured xcode-select correctly) for additional support:

 codesign -vvv -d $(xcode-select -p)/Applications/Simulator.app codesign -vvv $(xcode-select -p)/Applications/Simulator.app
+4
source

This happened to me when I ran a build script that ran the simulator directly before opening Xcode.

When you open Xcode for the first time, it will go through a validation process that takes a lot of time. After that, the contents of the package will also be checked, and you can use the simulator without warning.

If you still have a warning after verification, your version of Xcode may be compromised.

Perhaps this is a mistake that the gatekeeper does not warn you that the parent package has not been verified.

+4
source

In my case, I had several instances of Simulator.app present (some were downloaded directly from the Apple website, and not installed from the store). When I released open -b com.apple.iphonesimulator , one of the downloaded simulators was open, instead of the current one in /Applications/Xcode.app . I changed my command to open -a /Applications/Xcode.app/Contents/Developer/Applications/Simulator.app and the problem is now resolved.

0
source

More articles:


All Articles