Testing iOS apps. Failed to install the application. No code signature found

Question

I tried installing my application on multiple iOS devices. But that did not allow me.

I want to know what the problem is and how to solve it.

Answer 1

In my case, the problem was in unsigned frames: assembly phases> copy files> code mark on copy (check the boxes)

Answer 2

I had this problem, here is what I did to solve it:

• Run "clean" in Xcode
• Close Xcode
• Delete all data in ~ / Library / Developer / Xcode / DerivedData li>
• Delete all xuserdata folders in your project (check your xcodeproj and project.xcworkspace directories)

Only if you have Cocoapods in your project:

• Run the de-integration package.
• Delete your .xcworkspace if it was created by cocoapods.
• Run pod install or update

Now you can open your new Xcode.

Hope this helps you.

In my case, the problem was created by adding a new cocoa touch frame.

Answer 3

If the “code mark on copy” fails, check if you change the frameworks in the startup script after the “Embed frameworks” phase.

If you move the Run script to a position before the implementation phase of the framework.

Answer 4

In my case, I created an unsigned IPA file , and for this I made some changes to the SDKSetting.plist file (changed CODE_SIGNING_REQUIRED = NO), and it should always be YES if you run the application on the device.

To resolve this issue, follow these steps: Steps to create an unsigned IPA (tested on Xcode 9.4.1)

Step 1: Open Search> Go to Folder .. as shown below on the screen

and then copy and paste the following line:

/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS*.*.sdk/SDKSettings.plist

Open iPhoneOS.sdk as shown in the image below:

Step 2: Copy the SDKSettings list to another folder, because you cannot make changes here:

Step 3. Make changes in duplicate

set CODE_SIGNING_REQUIRED to YES

Step 4: Now replace the duplicate Plist with the original one (both names should be the same). This will also ask the administrator for permission to change.

********************************OR**************** * **********************

If you upgrade your Xcode, the problem will also disappear, because the updated Xcode will ship with SDKSetting.plist by default.

Answer 5

People, my problem. The root cause was the changes made by the iOSOpenDev installer. I restored the original plist file that was copied by the installer. which solved my problem, you need to look into the SDK directory to see if something scared has happened. at least one more option to try.

/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS<SDK version>.sdk/ 

example:

 /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS11.4.sdk/ 

by default, you must enable code signing; if it is disabled, something funky has happened. (for reference See Alok's answer below)
If all else fails. My recommendation would be to uninstall and reinstall Xcode, as this error will not occur in normal scripts. Therefore, restarting Xcode can significantly reduce troubleshooting time.

Answer 6

I also ran into the same problem. I tried all of the above solution, none of me worked.

Below things helped me

1. Choose build settings
2. Search for "Signature ID"
3. Choose "iOS Developer" or any other right option for everyone.

Then build and run.

Answer 7

1) Try to clean up the project 2) Try to restart Xcode 3) Reset your mac

Answer 8

Tried everything here and nothing worked except restarting my device.

Answer 9

I have some problems while loading the application in the Appstore, then I add some code in the build phase -> Run Script

done, I empty the Build folder and delete the above code from Run Script And Build again and run on my Iphone, everything works fine

You can delete the script launch code or check the box "Run the script only during installation", then it will work too

Answer 10

Turning on "Automatically manage my signature" solved the problem for me. (In goal settings, General tab, Signing section)

Answer 11

It is understood that you do not have a developer and distribution profile for the devices you are trying to install.