Xcode 7 - Error trying to integrate Parse using CocoaPods (Swift)

I am using Xcode 7 beta and I am trying to integrate the Parse iOS SDK using Cocoapods.

I already created bridging-header.h , I imported Parse #import <Parse/Parse.h> . I already called Parse in my AppDelegate.swift .

The error occurs when I try to use any class / object associated with Parse. Actually, I just call Parse with: Parse.setApplicationId(ParseAPI.AppID, clientKey: ParseAPI.ClientKey)

I get the following error:

 Undefined symbols for architecture x86_64: "_OBJC_CLASS_$_Parse", referenced from: type metadata accessor for ObjectiveC.Parse in AppDelegate.o ld: symbol(s) not found for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation) 

I cleaned the project many times even with a complete clean build .

+6
source share
3 answers

Using Xcode 7 beta 4, I first switched from using the Objective-C bridge header, removing all references to it in my Xcode project.

Then I updated my subfile with a new line at the top:

 use_frameworks! 

Then i ran

 pod outdated 

What told me about the new versions of Parse and ParseCrashReporting (from 1.7.5 to 1.7.5.3).

Then i ran

 pod update 

Opening my project in Xcode, the last step was to add import statements to the files in which I used Parse objects, so many files now included

 import Parse 

or

 import ParseCrashReporting 

For more information about use_frameworks, see http://www.innerexception.com/2015/05/cocoapods-useframeworks-means-bridging.html

+6
source

Finally, I could not solve the problem using CocoaPods.

I am using Xcode 7.2 beta strong>.

What I did, I imported Parse and Bolts manually according to the steps described in the Parse Doc .

I am currently having a different problem. Xcode 7 does not autocomplete any of the bridging-header , everything works fine, but not autocomplete.

I am not the only one who has this problem -> link .

+1
source

You need to add the bridge title to the workspace.

The parsing is written in Objective-C, so it does not match using the direct structure, as you did.

Here are some steps that might help: enter the link here

0
source

All Articles