× {{alert.msg}} Never ask again
Get notified about new tutorials RECEIVE NEW TUTORIALS

Swift : dyld: Library not loaded: @rpath/libswift_stdlib_core.dylib

John Grange
Nov 18, 2014
<p>I am sure that quite a few others have run into this issue, and it seems to even be a problem with newer iOS development accounts.</p><p><strong>Issue</strong></p><p>This issue will be exhibited when running swift code on an iOS device, and is most frequently present when deploying to internal users using an enterprise certificate.</p><p>The root of the problem is that the library is not properly signed and thus iOS 8 refuses to use the library causing your application to crash on launch. This can be caused by a few issues such as the certificate being created prior to iOS8 or possibly sometimes even the Xcode generated certificates.</p><p>One possible diagnostics tool is to check the signing certificate, if the subject line does not contain the field "OU" then you will need to revoke and regenerate the certificate and associated provisioning profiles.</p><p><strong>Incorrect:</strong></p><pre><code>Subject: UID=269J2W3P2L, CN=iPhone Distribution: Company Name, O=Company Name, C=FR</code></pre><p><strong>Correct:</strong></p><pre><code>Subject: UID=269J2W3P2L, CN=iPhone Distribution: Company Name, OU=269J2W3P2L, O=Company Name, C=FR</code></pre><p>You can easily check the certificate from the included provisioning profile in the IPA by pasting the binary certificate in the following URL: <a href="https://www.sslshopper.com/certificate-decoder.html">https://www.sslshopper.com/certificate-decoder.html</a></p><p><strong>Solution</strong></p><p>The solution is simple but in some development shops might be difficult, you MUST revoke the certificate, and generate a new certificate using the manual method (create certificate request in keychain assistant). Once you have completed this step you need to regenerate your provisioning profiles / recompile / redistribute. The app should now launch without issue.</p>
comments powered by Disqus