Xcode 8 "The application does not have a valid signature"

Question

Xcode 8 throws the following error even though the setup looks fine:

How to fix it?

Answer 1

It looks like an Xcode 8 error. Clearing a project by pressing Command + Shift + K or Product → Clear will fix it.

Answer 2

I had a similar problem, unfortunately, I would have to do a clean often, very expensive (~ 5-6 minutes) operation for my project and installation.

It turns out that this can be caused (during custom build phases) by adding a custom “BuildDate” field on my plist AFTER “Copying Bundle Resources” to display this value for debugging purposes in the application.

Not sure if the error was intentional or Xcode 8. I also found that doing any editing, even adding and removing a character to the code base, allowed me to start without having to do a full cleanup first.

Adding this entry to a separate plist BEFORE the build phase of "Copy Bundle Resources" and then extracting this plist for BuildDate (and not info.plist) solved the problem for me. More details in the provided source.

Source: https://forums.developer.apple.com/thread/63955 (I do not claim full credit for this fix, but a detailed fix solved the problem for me)

Answer 3

Another solution is updating the version number. It works, and you do not need to clean, which saves time.

Answer 4

In my case, Xcode shows this error in a rather random way. The simplest solution that works for me is to simply change one line of source code and build the project again. Just add an empty string.

Answer 5

In my case, this is a provisioning profile problem.

Here is the fix:

1) Select XcodeProject -> Target -> Signing -> Team as None. 2) XCode -> Preferences -> Accounts -> Apple IDs -> (Remove the apple Id once, please make sure you should have apple id credentials in order to add it again) 3) Add the apple ID again. 4) Quit Xcode. 5) Open Xcode 6) Select XcodeProject -> Target -> Signing - > Select the new Team added. 

Now it should work.

Answer 6

This error occurred to me when I tried to install an .app format application on a physical iOS device. Make sure that you are trying to install on the correct device type.

Answer 7

In my case, one of the platforms was configured for a deployment target of 12.0, which is higher than my actual launch device. The fix for the lower version worked.

Answer 8

I had the same problem with watchOS application; the only thing I could solve was to clear all the Provisioning Profiles profiles by deleting them from ~/Library/MobileDevice/Provisioning Profiles/ and then allowing Xcode to reload what it needs (I allow Xcode to automatically control signing).

Answer 9

In my case, the problem was in my own framework libraries that had a "deployment target" of 12.1, which was set by default when creating Xcode. The main application to which I added these libraries had a "Deployment Goal" of 9.3. The problem occurred when deploying to an iOS 10 physical device. Installing the framework libraries on the same "deployment target" as the application solved the problem.

My guess is that the obvious rule of thumb is to set up frameworks for deployment purposes that are "older" than the target application. It’s my fault, but I would prefer some warnings and fewer cryptic errors for such a case. Xcode 10.

Answer 10

For me, the message disappeared after I upgraded iOS from 10.3.3 to 12.3.1 on the device where I was trying to run the application.