New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dyld: Library not loaded: @rpath/libswiftCore.dylib #9
Comments
Yes, I followed the setup instructions exactly. This is likely an Apple bug as a swift lib is not being found. A quick search on stackoverflow reveals numerous questions about this for other apps using a swift framework. My comment about using ObjC is born out of frustration with swift issues like this, swift being not quite ready for production code. Thanks for your quick reply. |
For an update, the swift example works great! This appears to be an Apple bug with an ObjC app using a swift framework. I'll see if I can figure anything out here. |
Same issue here. With Obj-C example, I get error
I have added the libraries to Embeded Frameworks and still same error. |
Same issue, I am trying to run Swift example with cocoa pods, at first I was getting error
To resolve the above error I tried to use swift 3.0.2, then I am getting below error
|
@jasmeet12 Thanks for reporting the issue. Can you share command line output when you run 'pod install'? You might not get the latest version due to pod bug. |
@bingh0616 Please find output |
@jasmeet12 Our latest version is 2.2.2, do not know why pod give you 2.1.1 version. Can you try 'pod update' and then try to build using latest xcode and swift. Thanks |
I tried that Now version is 2.2.2 and now I am able to run the build thanks for the quick reply :) |
@jasmeet12 No problem, we will try to see what we can do with the pod install bug. Thanks |
I faced the app crash issue quoting SIGABRT error in thread.Overview of the crash is dyld library not loaded and image not found something like that. This was seen in xcode 9.3 version.The reason i found out was xcode is not picking up libraries dynamically so i had to do it manually which solved my crash issue. Follow the below steps: Step 1: Go to Build Phases Step 2: Hit the '+' button at the top and select "New Copy File Phase" Step 3 : Select Destination as Frameworks and Hit the '+' button below to add files. Step 4 : Select Add Other at below, click CMD+SHIFT+G and paste the below path, /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/swift/iphoneos Now you will be able to see some swift dylibs, Select all the swift libraries with .dylib extension and click on open. These will get added to the embedded binaries in the general tab of app. Create a new group in project folder and add all these libraries. Now run your app. Happy Coding |
@miyamirz @Pranoy1c do you know if this is a Xcode 9.3 only, i.e. is it fixed in recently released Xcode 9.4? My own private framework cannot run its own test target due to I got rejection when uploading to iTunesConnect when uploading the IPA, with error message:
|
For what it's worth, I hit a similar error in XCode 9.0.1. I tried uninstalling and reinstalling all my certs, but when I reinstalled, they seemed to remember the trust setting I had previously. What ended up working for me (it seems) was turning off the 'Always Trust' setting of the "Apple Worldwide Developer Relations Certification Authority" cert followed by a reboot. What a cryptic issue! |
@Sajjon Need to check on that. |
Using Xcode 8, it builds fine but is crashing right after launch with this error:
dyld: Library not loaded: @rpath/libswiftCore.dylib
Referenced from: /Users/Jim/Library/Developer/CoreSimulator/Devices/71C3C61E-1604-48FF-813F-84985541B72A/data/Containers/Bundle/Application/850D7F48-B1CD-4FA8-A0C8-41ED890CF1CE/TCMaskPopView.app/Frameworks/TCMask.framework/TCMask
Reason: image not found
I've tried everything so far and no luck:
Is there any chance you can do an Objective C framework that doesn't rely on swift? This looks like a great framework and might be exactly what I need.
Thanks!
James
The text was updated successfully, but these errors were encountered: