I just recently updated to Xcode 7 as well as Swift 2 and quickly ran into errors when retrieving PFFile's due to App Transport Security. So I updated to the most recent Parse SDK. I deleted from my project:
Bolts.framework
Parse.framework
ParseFacebookUtilsV4.framework
ParseUI.framework
and then dragged the same, updated, frameworks over into my project folder. Now, after cleaning and building, I am receiving errors within PFFacebookUtils.h: Include of non-modular header inside framework module 'ParseFacebookUtilsV4.PFFacebookUtils' on lines where there is declared:
#import <FBSDKCoreKit/FBSDKAccessToken.h>
#import <FBSDKLoginKit/FBSDKLoginManager.h>
Has anyone ran into and solved this issue yet?
Also, I already have "Allow Non-Modular includes in framework modules" set to "Yes"
ParseFacebookUtilsV4 includes the Parse framework. Try deleting the Parse part. It could be causing build errors, it was messing my Parse project up.
What did it for me was changing the original #import <ParseFacebookUtilsV4/ParseFacebookUtils.h> in my bridging header to:
#import <ParseFacebookUtilsV4/ParseFacebookUtilsV4.h>
Note the added "V4" at the end.
Related
Getting this weird error suddenly.
I have tried cleaning and deleting the derived data and also tried changing the Enable modules flag in build settings.
Does anyone know how to fix this errors in Xcode.
EDIT: The errors only show up while archiving, I can successfully build and run in Simulator.
It can be easily reproduced by just installing Core plot and Google speech api together via Cocoapods.
Had the same issue, fixed by replacing #import <CommonCrypto/CommonCrypto.h> with #import <CommonCrypto/CommonHMAC.h> in my Swift bridging header file. The former includes CommonKeyDerivation.h, which eventually include time.h. However, gRPC has a time.h file as well, as it has header priority in header search path, its timer.h version is used instead of the system one, which caused to the issue you mentioned. Hope this helps.
I am trying to use google maps in my ios app my Xcode ver is 7.2 and swift ver is 2.1.1. I simply add GoogleMaps in my pod file everything is fine i added frameworks and libs which are required to support Googlemaps all fine, i am following this tut and according to this i have to add a bridging header file to include
#import <GoogleMaps/GoogleMaps.h>. My app already have one bridging header file because i am using facebook login as well so i put the import statement in the same file and in 'others linker flag -ObjC' is already there so after few required settings in storyboard i compiled my proj but i am getting this error "GoogleMaps/GoogleMaps.h" not found. I have searched for it and tried almost all the suggested ways on Stackoverflow but hard luck nothing worked yet.I will be really grateful if anyone could suggest me what i am doing wrong here.
Make sure your pod install went smoothly.
According to the tutorial,
You should see output similar to the following:
Downloading dependencies
Installing GoogleMaps (1.10.4)
Using SwiftyJSON (2.3.0)
Generating Pods project
Integrating client project
try
#import "GoogleMaps.h"
in your bridging header file
I updated to xCode 7.1 today and tried to build my app but I'm getting this error:
I have already tried going to Build Settings under "Target" and set "Allow Non-modular Includes in Framework Modules" to YES but that didn't solve this issue.
UPDATE: Since this was preventing me from compiling and hindering my progress in terms of development, I recommend you download an older version of xCode from Apple (https://developer.apple.com/downloads/ make sure to login). You can download version 7.0.1 from the link and at least continue development.
This is what I've done and I can continue development.
I know this is not a fix, but its workaround for the people who wish to continue development.
Google has updated its SDK to 1.10.5, Just Reinstall Pod and it should work fine. I was facing same issue and now all issues are fixed after pod reinstallation.
I ended up having to create an Objective-C bridging header file and adding #import <GoogleMaps/GoogleMaps.h> whereas I hadn't needed one previously since I was using Cocoapods in a Swift project and the use_frameworks! setting had previously taken care of this.
Here's instructions for how to create the Objective-C bridging header file: (https://developer.apple.com/library/ios/documentation/Swift/Conceptual/BuildingCocoaApps/MixandMatch.html)
https://forums.developer.apple.com/thread/23554
Just remove the header search paths in build settings. In new Xcode versions (after 7.0 I guess) you need to look for the headers by linking frameworks and not by linking header files directly.
For me, this issue was resolved by:
Product > Clean (cmd k)
Product > Clean Build Folder (cmd opt k)
Product > Run (cmd r)
This thread may be useful.
I tried a few things, but I'm not positive which one fixed the issues.
First, I edited my Podfile to include:
post_install do |installer|
installer.pods_project.build_configuration_list.build_configurations.each do |configuration|
configuration.build_settings['CLANG_ALLOW_NON_MODULAR_INCLUDES_IN_FRAMEWORK_MODULES'] = 'YES'
end
end
Then, I added a bridging header file, with one line:
#import <GoogleMaps/GoogleMaps.h>
Cleaned and rebuilt the project and that did the trick.
I import the Facebook AsyncDisplayKit framework into my app using the swift bridging header, like so:
#import <AsyncDisplayKit/AsyncDisplayKit.h>
It's always worked fine for building and running my app, but when I go to archive, it gives me an error:
import 'file not found'
Why might this not be recognized, upon archiving?
I always meet this kind of problem. I think you can try to check your file&folder hierarchy.
Such as you have a root folder named Project, as is often the case, there is another Project in your previous Project, the root folder.
And Checking the Objective-C Bridging Header in the Build Setting. Sometime error can occurred for Project/Project/Bridging-Header.h. And the error can be corrected by changing the definition as Project/Bridging-Header.h.
If the location of Bridging-Header.h is not matching with the definition in the Build Setting, the error like import file not found will occur.
I just tell your my solution for Bridging issue I already met, I hope it can help you.
I imported a header file to a swift project.
The header file contained inputs to Parse obj c libraries.
Everything worked fine I tested with Parse no problem.
When I saved then closed the project then re-opned I get a compiler error saying the Header file cannot be found. Here is the error.
failed to import bridging header '/Users/callanmooneys/Desktop/iOS
Deveolpment/Swit/Lab cases Haematology/Lab Maternity Haematology/Lab
Maternity Haematology-Bridging-Header.h'
Tried everything here:
Swift Bridging Header import issue
I don't understand how all worked fine until I saved the project the re-opened it.
Any input appreciated.
You should also try:
cleaning the build folder using Shift-CMD-Option-K
check the build settings to be sure that the correct bridging header with correct path is selected
deleting the bridging header, but only deleting the reference. Then, quit XCode and on relaunch, re-add your bridging header to your project
creating a Objective-C header, copying the code of your old header in there, and then setting the new header as your bridging header in project settings
EDIT:
try saving the file without spaces
Even if Swift isn't in beta anymore, there are still some bugs. So you should try several things.
Delete derived Data
Clean your Project: Product -> Clean
Edit the search path (First answer)
Check that your .h file etc is still available and you didn't delete it by mistake.
This has been happening to me whenever I use an Obj-C Bridging Header in any of my projects.
Whenever I launch, I get the same error, along with another one that goes something like:
Parse/Parse.h file not found
Every time I launch Xcode, I delete the Parse.framework from my Xcode project completely, then drag it back in.
This fixes the issue for me until I quit Xcode, and then I will repeat upon relaunch.
This has been happening to me for many months, not only with Parse, but it's also happened with RevMobAds.framework. I've gotten used to deleting and reinstalling the frameworks each launch.