Xcode 11.2 - Unable to install App file to device?

Question

I recently updated my OS to Catalina, and updated Xcode to 11.2. Since doing so, when I try to run a release version of my app on my device, I\'m simply given the error:

Answer 1

For me, it was that the watch i was trying to use didn't unlock so i had to lock and unlock my watch again and then it was working fine.

Answer 2

Go to File -> Workspace Settings, and make sure your build system is set to Legacy Build System.

I ran into the same issue on Catalina and Xcode 11.2 and this solved it for me.

As of Xcode 11 Apple is starting to enforce some of the build criteria that was previously only required for AppStore builds on .ipa extraction, and device builds.

So far I have encountered:

• Requiring the above legacy build system setting for device deployments for older projects or projects that use older frameworks
• Removing unused architectures to extract an ipa from an archive

Answer 3

I manage to fix this issue when first I clean:

cmd + k
shift + cmd + k

and then I delete all the content of Deriving Data the path of the folder should be like this

/Users/youruser/Library/Developer/Xcode/DerivedData

Or you can check it in

Xcode -> Preferences -> Locations

Answer 4

This is a codesign problem.

You can check iOS device logs to see which framework go wrong. filter 'installd' process. you can clearly say which framework codesign is wrong. so just find it out and fix it!

0x16fa53000 +[MICodeSigningVerifier _validateSignatureAndCopyInfoForURL:withOptions:error:]: 77: Failed to verify code signature of /var/installd/Library/Caches/com.apple.mobile.installd.staging/temp.dABVKh/extracted/Your.app/Frameworks/xxx.framework : 0xe8008001 (An unknown error has occurred.)
0x16fa53000 -[MIInstaller performInstallationWithError:]: Verification stage failed

Answer 5

Delete derivedData folder

rm -rf ~/Library/Developer/Xcode/DerivedData

Answer 6

This issue is only related to CODE SIGNING

But, the key point to note here is, if you are using XCode 11.x version. Not only the code signing in your project, but we should check the code signing in Thirdparty SDKs or dependencies that we add to our project.

Steps to verify the Code Signing of 3rd party SDks:

1. Download the source code of framework you need
2. Open the .xcproj file from the source code using XCode 11.x

3. Go to Targets -> Signing & Capabilities -> Select all tab -> Bundle Identifier If you see any unevenness in the identifier like, identifier with 4 seperators (Eg: com.company.mac.app)

   Change it to com.* and enter.

4. Make sure your XCODE COMMAND LINE TOOLS is set with XCode 11.x

5. Now, use below command to rebuild the SDK, with the changes done in above step-3

     carthage build --no-skip-current --cache-builds --platform iOS
   

6. Now copy the framework generated from, carthage folder of source code, and replace the existing SDK in your project.

Repeat the same for process for all the 3rd party SDKs, in your project.

NOTE: Make sure you marked all the 3rd party SDKs as Embed & Sign in

Targets => General => Frameworks, Libraries, and Embedded Content