2) Make sure you have added your binaries through "Embed Binaries" section.
3) Make sure you have enabled signing of frameworks in build phase section.
4) Make sure the embedded frameworks are not symlinks.
5) You can make the linked frameworks optional instead of required in "Link binary with libraries" phase. This will tell iOS to not look for these frameworks during launch. But anyway you need to fix the errors to use those frameworks!
6) Check if all the info.plist entries are good. In my case, I was using a Mac info.plist file for iOS. It was looking for some xib file which was not present in iOS project.
7) Do a clean and build after any such change. This is required because xcode does not copy/change these files if they already exist.
8) Remove the app from iPad and then install. Same reason as 7.
I've just had the same issue and the reason why was due to the fact that I've revoked my Developer Certificates and created new ones with Xcode 10, after a fresh macOS Mojave update (for some it deleted all login credentials and outdated some keychain certificates).
So, All I had to do was to remove the installed apps from my device and run them through Xcode again, in order for it to install the right new Provisioning Profile in my device :)
1) Continue the execution to see if any message shows up in debugger such as "MyFramework.framework" not found. If that is the case, follow this discussion: OS X Framework Library not loaded: 'Image not found' For me this answer worked:https://stackoverflow.com/a/44796734/4060763
2) Make sure you have added your binaries through "Embed Binaries" section.
3) Make sure you have enabled signing of frameworks in build phase section.
4) Make sure the embedded frameworks are not symlinks.
5) You can make the linked frameworks optional instead of required in "Link binary with libraries" phase. This will tell iOS to not look for these frameworks during launch. But anyway you need to fix the errors to use those frameworks!
6) Check if all the info.plist entries are good. In my case, I was using a Mac info.plist file for iOS. It was looking for some xib file which was not present in iOS project.
7) Do a clean and build after any such change. This is required because xcode does not copy/change these files if they already exist.
8) Remove the app from iPad and then install. Same reason as 7.
I find the right way to resolve it.
Make sure the
AppleWWDRCA.cer
be set system default mode, then it will work:if you use Carthage build framework, after drag the framework to your proj, you should add it to General/Embeded Binaries.
I've just had the same issue and the reason why was due to the fact that I've revoked my Developer Certificates and created new ones with Xcode 10, after a fresh macOS Mojave update (for some it deleted all login credentials and outdated some keychain certificates).
So, All I had to do was to remove the installed apps from my device and run them through Xcode again, in order for it to install the right new Provisioning Profile in my device :)
I got it sorted by "pod install" command.
Unchecking "Guard Malloc" in diagnostics worked for me.