I am trying to import Parse and Bolts frameworks, but the Xcode is unable to build the project. I tried following ways, but nothing seems to work out :
Creating groups, and copying the folder.
Cleaning the project and Deleting the derived data.
Importing the frameworks into the project and create references.
I am using Xcode 7.0 beta (swift 2.0). Screenshot of the same is attached.
Cheers and thanks in advance!![
I had a similar issue, but I was using cocoapods, as shown in parse.com docs (but they are not yet updated for XCode7 and Swift2).
I just added use_frameworks! to my Podfile
source 'https://github.com/CocoaPods/Specs.git'
platform :ios, '8.0'
use_frameworks!
pod 'Bolts'
pod 'Parse'
I had the same error and I wrote in the support of the parse and they answered me that they would update for the swift 2 when Xcode 7 will get out from a beta version.
Them answer "We plan to support Swift 2 and Xcode 7 by the time they go out of beta. Currently, there's only one initial beta release of Xcode and iOS 9, and typically a lot of things change before Beta 3 or 4 is released. We'll be keeping a close eye on things and do a release once things settled down. We're tracking any issues reported around Swift 2 and Xcode 7: please file a bug! https://parse.com/help#report".
I had the same problem on XCode 7 beta 6 and the 7.1
It seems that XCode does not "like" to import frameworks from a "relative" location (in this case I was importing the framework from the download folder)
I have copied the libraries in the "Frameworks" directory and imported them in the project. From there and they work.
I had the same problem.
I just deleted the Parse Frameworks and added the objective-c ones with a riding-header. Now it works.
Related
I am integrating FrirebaseCrashlytics SDK in tvOS and iOS without cocopods. I downloaded their xcFramework. But I can't use the xcFramework as the project is not compatible so I drag and drop ios-armv7_arm64 framework to project and added Firebase.h and module.modulemap (my project uses both objc and swift). Also, I specified the Firebase.h in the bridging header. I get below error when I build.
Showing Recent Errors Only
/Users/xxxxx/Code/ios/tvOSApplications/App/App/Firebase.h:15:9: 'FirebaseCore/FirebaseCore.h' file not found
Showing Recent Errors Only
/Users/xxxxx/Code/ios/tvOSApplications/App/App/App-tvOS-Bridging-Header.h:27:9: Could not build module 'Firebase'
Multiple problems to address (based on instructions in the README at the base of the distribution:
The zip distribution requires Xcode 11 which supports xcframeworks
The zip distribution only supports iOS. tvOS is only distributed via CocoaPods
All Firebase installations require the xcframeworks in the Analytics folder to also be installed.
I am able to get firebasecrashlytic .framework files without cocopods using Carthage. I copied files to project and it works in iOS project. I am looking for a similar solution for tvOS
Recently I had a similar requirement of supporting Firebase on both iOS and tvOS. As the frameworks are available only on iOS and not on tvOS. I could not integrate Frameworks. So the solution I followed is adding of Source files provided in https://github.com/firebase/firebase-ios-sdk corresponding to the required modules that are needed for enabling Firebase Crashlytics.
This solution worked for me and able to see the crashes. Let me know if you need more information
I got Firebase Crashlytics working for tvOS without Cocoapods or XCFramework bundles. Basically, you just need to bring over the source files, set the header search paths, and set all the required preprocessor macros. You can read the story here.
Thanks for the hint Gangadhar!
I want to use Hero framework. I don't get any pod command from their documentation. I have used pod "Hero". It's worked but after installing and downloading pod when try to open project it says
Xcode 9 does not support building or migrating Swift 2.x targets"
How can i solve this?
You can find the pod installation section in their documentation here.
If the process not work you try to read more...
This error means that XCode 9 does not offer any solution to migrate from Swift 2 to 4.
In fact into Build Setting you can switch from Swift 3.2 or 4.
You can try to open the project with XCode 8 firstly (that support Swift 2) and then after converting the library to Swift 3, reopen the project with XCode 9.
My Swift 4 app rebuilds and runs successfully on all simulators except for Generic iOS Device. If I try to archive it or do a rebuild on Generic iOS Device, I get a No such module error relating to one of my pod frameworks.
I tried adding the framework to Linked Frameworks and Libraries, and that removed the error, but then it fails on the next pod framework, and so on. I have tried all sorts of paths in Framework Search Paths with no luck.
Currently, the value is set to:
I even tried deleting the workspace, the pod lock file, and the pods folder, and then I did a pod install to rebuild everything. Again, it rebuilds clean on any simulator except the generic one. On the generic one, I get No such module on all import statements for pod frameworks.
Any suggestions appreciated, as this problem has me completely stalled, since I can't get a release out.
For me what fixed it was removing one line from my Podfile and rerun pod install.
platform :ios, '11.0'
I think the version of the pods was not aligned with the version of my target, causing this issue.
I was able to fix the problem editing the ios version line in the Podfile to match the Project target version (10.0 in this case) in Info.
#Podfile
platform :ios, '10.0'
Finally I had to run
pod update
After that, I was able to Archive my project selecting Generic iOS Device
In my case I had selected a Device on Xcode when archiving, choosing Generic iOS Device solved my problem.
It's better to check the project settings by going to Build Settings, find Framework Search Paths and add $(SRCROOT) and be sure it's recursive.
I kept facing the issue "No such module" while archiving the app.
I tried this approved answer and it worked perfectly but, a new warning was appearing in my Podifle.
So I did the below and it worked without any warning.
Podfile :
XCode -> Targets -> My App -> General :
switched iOS from 10.0 to 11.0 and then everything worked perfectly.
Seems like by opening up the project by double clicking Runner.xcworkspace instead of Runner.xcodeproj, xcode can finally figure out where everything is. Even though you can still debug in an emulator and on a connected phone from the .xcodeproj file...
Seems strange that it would fix it. But I'm happy to have an Archived build now.
Check out this link for more info
There is another case similar to the same error. when you have an Embedded Framework project with min iOS 10 (Any iOS Device arm64, arm7) while I am archiving the build of the project with min deployment version iOS 11(Any iOS Device amr64) in Xcode 12.5.1.
I have to change the min deployment version of the Embedded Framework project to iOS 11(Any iOS Device amr64) to match with my project's deployment version.
first build your project command + b and see if the frameworks are in red when you look at then at the right sidebar, if they are, xcode did not find your files on the specified path, if not, building and then archiving should work
I was able to get it to archive by re-creating the project from scratch. I created a new project, used the same pod file to install the pod libraries, then copied everything over from the other project. I am now able to archive it and push it to the store. Must have been some corruption or a rogue setting.
In my case, the module which couldn't be found was a dynamic Obj-C framework with a minimum deployment target higher than my application project's minimum deployment target. Bumping my minimum version fixed it, but you could drop the version on the framework instead.
I want to archive my app with selecting the Build Option "Generic iOS Device" (and i've done that a couple of times before i upgraded to Xcode 9.2) but unfortunatly it fails every time saying "No such module 'CryptoSwift'".
To make it clear, it doesn't have to do anything with SwiftyBeaver; it maybe have to do with my CocoaPods, maybe they don't like that libraries against the target. Or maybe with Xcode 9.2 itself.
To be more specific, it fails here:
import CryptoSwift //No such module 'CryptoSwift'
Whenever i select the simulator or a device (for building, not archiving), it compiles and everything works as expected.
Any suggestions?
The answere was in the first line of my cocoa pod file:
platform :ios, '11.0'
Instead of using 11.0, i changed it platform :ios, '11'.
And than i had to change the deployment target to 11.2. I don't know, what that was changed to 10.0 but those two changes did it.
So if you guys are using any minor versions of iOS in your pod file and you aren't sure, if it exists, just leave it blank!
Apparently it did cause those No such module '' errors, because the compiler wasn't able to build that frameworks in the Derived folder because it didn't know what iOS Version i wanted them to be built.
After updating to the recently released beta 6 of Xcode 6, my swift project fails to build due to the following errors.
Looking at previous questions on this issue, propose checking the build architecture is set to support arm which mine project includes already (arm64, armv7s, armv7).
First, make sure you have the most recent beta installed. Afterwards delete your DerivedData folder ( ~/Library/Developer/Xcode/DerivedData ). This should allow you to compile again in the latest beta.
Edit: This appears to hold true for the newest beta version of the Xcode as well
From what I hear, so far Xcode 6 Beta 6 is broken. You should uninstall and rollback to Beta 5.
Edit:
Apparently, a new version is already out, just reinstall beta 6
http://9to5mac.com/2014/08/18/apple-re-releases-xcode-6-beta-6-solves-issues-discovered-by-developers-in-new-build/
Make sure you install the latest Xcode Beta 6 version. If you check Xcode->About Xcode, you should see: Version 6.0 (6A280e)
I had the same problem. I reinstalled Xcode. then it fixed the problem.
In my case it happened because of deleting a imported framework(move to trash) which is inside my project navigator. I think Xcode delete the whole framework when we delete(move to trash) imported framework from our project navigator.
Make sure you haven't done any unnecessary imports example importing an .h file when you needed .m