Undefined symbols for architecture i386: _OBJC_CLASS_$_SKPSMTPMessage", referenced from: error

IosObjective CIphoneCompiler ErrorsEmail

Ios Problem Overview


I have imported framework for sending email from application in background i.e. SKPSMTPMessage Framework. Can somebody suggest why below error is shown

Undefined symbols for architecture i386:

"_OBJC_CLASS_$_SKPSMTPMessage", referenced from:
  objc-class-ref in ConfirmController.o

"_kSKPSMTPPartContentTransferEncodingKey", referenced from:
  -[ConfirmController sendEmail] in ConfirmController.o

"_kSKPSMTPPartMessageKey", referenced from:
  -[ConfirmController sendEmail] in ConfirmController.o

"_kSKPSMTPPartContentTypeKey", referenced from:
  -[ConfirmController sendEmail] in ConfirmController.o

ld: symbol(s) not found for architecture i386
collect2: ld returned 1 exit status

Source from which framework is taken:-

https://stackoverflow.com/questions/6284599/mfmailcomposeviewcontroller-question-locking-the-fields/6287412#6287412

Update:

Answer:Just drag and drop folder over the project and click copy. Thats it select project check box and target check box as well.

Ios Solutions


Solution 1 - Ios

You can get this type of error if your class' .m file is not listed under the "Compile Sources" step of the "Build Phases" tab of your target. Normally Xcode does this for you, but sometimes it loses the plot and you need to add the .m file manually.

To do this:

TargetSettings -> Build Phases -> Compile Sources -> add your .m class ->Build and Run

Solution 2 - Ios

for me the issue turned out to be missing frameworks. Once I added em, it worked.

Solution 3 - Ios

Check the Valid Architectures & Build Active Architecture only properties.

enter image description here

Solution 4 - Ios

if you are using cocoapods make sure your target's build settings contain $(inherited) in the other linker flags section

enter image description here

Solution 5 - Ios

Is your framework compiled for armv(x)? It looks to me like it's compiled for i386, which code won't run on an iOS device. Or else it's compiled for armv(x) and you're trying to run it on the simulator, which is i386 code. Make sure, using the build settings Akshay displayed above, that your framework is correctly compiled for the chip you're going to run it on.

Solution 6 - Ios

If you importing some other project in xcode and if current and import project both have same files in Compiler source then just remove same file in current project in "Build phase' settings. It worked for me.

Solution 7 - Ios

Yeah this is related to what allen said... look for TargetMembership in Utilities section of the source file. there is a checkbox that associates that file to a project. Checking this solved this issue for me too.

Solution 8 - Ios

Also could be that you're missing to link against a Binary Library, check Build Phases in your Targes add required libraries and then Product > Clean Product > Build

That must work too!

Solution 9 - Ios

I had this issue when I opened the same project twice, only one project was the original and the other was cloned from a git url.

'Product' > 'Clean' solved the problem.

Solution 10 - Ios

try this one last:

so I tried all the suggestions on this page.. none worked.. The way my problem started was by following the steps in this tutorial that teaches how to link static libraries. With my sample project the instructions worked fine.. but then on my actual project I started getting the error above.

So what I did was go through each step of the said tutorial and built after each step.. the offending line turned out to be this one: adding -all_load to build settings-> other linker flags

it turns out that this flag was recommended once upon a time to link categories to static libraries.. but then it turned out that this flag was no longer necessary Xcode 4.2+.. (same goes for the -force_load flag.. which was also recommended in other posts)..

Solution 11 - Ios

When I encountered the same problem as this:

> Undefined symbols for architecture i386: > > OBJC_CLASS$_SKPSMTPMessage, referenced from: objc-class-ref in ConfirmController.o

It turned out that I just forgot to add framework. It was QuartzCore.framework to be exact.

Solution 12 - Ios

I also met this issue and I fixed it by checking if both compile source and link binary with library contained all the file/library/framework I required.

enter image description here

Solution 13 - Ios

When I encountered the same problem, i forgot to add "compiled version of library(with extension .a)". Normally we add the library of the imported project in Target Dependency in Build Phases but we forget to add "compiled library" in Link Binary with Libraries in Build Phases.

Solution 14 - Ios

Adding what worked for me in case others have the same issue and end up here. I had an older project that had the CLANG_ENABLE_MODULES setting set to No. After hours of frustration I compared to a working project and found I had Enable Modules Set to no under my LLVM build settings. Setting this to Yes solved my problem and the app builds fine.

Project Settings -> Build Settings -> search for 'Modules' and Update Enable Modules (C and Objective-C) to YES.

Solution 15 - Ios

Change in active architecture worked for me, One of my lib was using i386.

In build settings >> change Build Active Architecture Only to Yes from NO

It worked for me. Hope it helps to others as well.

enter image description here

Solution 16 - Ios

I didnt add the "-all_load -lstdc++" to Other Linker Flags in the build setting and I was able to launch the sim without error but I did not get MonkeyTalk log output when launched and the a previous script that I wrote that used to connect now showed the play button as disabled. The output of the MT IDE showed as "Connection set to iOS Simulator", but not able to select the run/play button.

The original project had "ObjC -all_load" in the Other Linker Flags and when I appended the "-all_load -lstdc++" along with it I got the error message this post is about. When I removed the "ObjC -all_load" and only added the "-all_load -lstdc++" the project built, but still no monkey talk log out put as confirmation in the console

Solution 17 - Ios

It's possible you're using a library that is only compiled for REAL hardware. For example, if you're using a Bluetooth library like the Zephyr HxM Smart, it probably won't compile on the simulator, and is only meant to run on real devices.

Solution 18 - Ios

I discovered this HIGHLY misleading message while trying to upgrade to the new Google Analytics library.

In my case the problem was having TWO CONFLICTING COPIES of the library. They were in different folders but both were listed in my App's Library Build Paths (under Build Settings).

Moving all the deprecated library files out of the folder ended up doing the trick and made the mysterious error messages go away.

Solution 19 - Ios

Ran into a similar issue with IOS 6. Was able to solve it by adding storekit.framework to the "Link Binary with Libraries" in the build phases section.

Now, it works like a charm.

Solution 20 - Ios

i have the same problem with 7 errors when i add PSTCollectionviewcontroller .The one solution for this problem is check your "xcode --> build phases-->compile sources" here add your all ".m" files ..I hope you this post will help users in future.

Solution 21 - Ios

On mine, I was using Cocoapods for an Augmented Reality project and what I found out was that when you implement cocoapods and open your project's .workspace, you end up with the Xcode Project target and those Pods target you implemented inside the same file. What was happening was that some of the .m were being used by both. After I removed the duplicated ones for the Xcode target at Build Phases >> Compile Sources, it worked fine.

Solution 22 - Ios

Check that all your bundle resources are copied in build phase.

Solution 23 - Ios

Product => Clean did the trick for me

Solution 24 - Ios

Answer is you just drag and drop folder over the project and click copy.

Solution 25 - Ios

I got this message when I drag and dropped some source files from another project. When I deleted them and then added them via the "Add Files..." from the File menu, it built without the error.

Solution 26 - Ios

I had a similar error with NSManagedObject and it was because I was using Core Data but was missing the Core Data framework in Build Phases - Link Binary With Libraries, as some others have answered

Solution 27 - Ios

You can get this type of error if you add third party libraries in your project that require native frameworks not included in your project.

You need to look inside the .h and .m files of your newly added library and see what frameworks it requires, then include those frameworks in your project (Target > Build Phases > Link Binary With Libraries).

Solution 28 - Ios

Try remove the framework, clean project, add it back and compile. Or Remove the class which has been added by xcode in compile source, clean project, add it back then build.

Solution 29 - Ios

Remember That you can put some macro in any view controller which is calling the files you've already deleted.

The app will not show any errors until you build your app, it will throw the error in compilation phase in .o files.

Remember to delete any MACRO that's calling to files you've already deleted.

Thanks :)

Solution 30 - Ios

In addition to what Allan did, adding missing classes, I followed @emdog4's solution and added the Core Data library by going to Build Phases in Xcode and under the 'Link Binary with Libraries' clicking on the + and selecting the 'CoreData.framework'. This sorted out my error

Solution 31 - Ios

In my case it was a bit different

In the Prefix Header there was a define missing

#ifdef DEBUG
#   define TWDLog(fmt, ...) NSLog((@"\n%s\n" fmt), __PRETTY_FUNCTION__, ##__VA_ARGS__)
#else
#   define TWDLog(...)
#endif

So search for PROJECTNAME-Prefix.pch and check if it has something missing in both projects

Solution 32 - Ios

I got the same issue. And I add 2 framework I need to Build Phases. Hope this help! symbol(s) not found for architecture i386

Solution 33 - Ios

In my case the pod update didn't update the project somehow. So I had to do it by myself, adding the MBProgressHud to OtherLinkerFlags.

enter image description here

Solution 34 - Ios

None of the above answer solved my issue. I got this same error when after I upgraded Xcode to 8, I went to Target --> Build Phases --> The Link Binary With Libraries and delete the framework that caused the problem and re added it and all the errors went away. Hope this will help others. enter image description here

Solution 35 - Ios

Just enable the "Build Active Architecture Only" option

in PROJECT >> Build Settings >> Build Active Architecture Only >> Yes

screenshot of the path to the configuration

remember to check if they are also enabled in each target

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionMannView Question on Stackoverflow
Solution 1 - IosAllen PikeView Answer on Stackoverflow
Solution 2 - IosvermaView Answer on Stackoverflow
Solution 3 - IosAkshayView Answer on Stackoverflow
Solution 4 - IosTimView Answer on Stackoverflow
Solution 5 - IosOwen HartnettView Answer on Stackoverflow
Solution 6 - IosDPPView Answer on Stackoverflow
Solution 7 - IosyeahdixonView Answer on Stackoverflow
Solution 8 - IosGabriel RamirezView Answer on Stackoverflow
Solution 9 - IoskraftydevilView Answer on Stackoverflow
Solution 10 - IosabboodView Answer on Stackoverflow
Solution 11 - IosMitch VirayView Answer on Stackoverflow
Solution 12 - IosyujohnnyzhouView Answer on Stackoverflow
Solution 13 - IosBalamuruganView Answer on Stackoverflow
Solution 14 - IosjlichtiView Answer on Stackoverflow
Solution 15 - IosSatish MavaniView Answer on Stackoverflow
Solution 16 - IosLaser HawkView Answer on Stackoverflow
Solution 17 - IosDiscDevView Answer on Stackoverflow
Solution 18 - IosbkbeachlabsView Answer on Stackoverflow
Solution 19 - IosTroyView Answer on Stackoverflow
Solution 20 - IosNaveenView Answer on Stackoverflow
Solution 21 - IosJoao PauloView Answer on Stackoverflow
Solution 22 - IosArpan DixitView Answer on Stackoverflow
Solution 23 - IosYogevSittonView Answer on Stackoverflow
Solution 24 - IosMannView Answer on Stackoverflow
Solution 25 - IosRyeMAC3View Answer on Stackoverflow
Solution 26 - IosSamView Answer on Stackoverflow
Solution 27 - IosCosminView Answer on Stackoverflow
Solution 28 - IosSaifView Answer on Stackoverflow
Solution 29 - IosAtefView Answer on Stackoverflow
Solution 30 - IosmalkotyView Answer on Stackoverflow
Solution 31 - IosShereef MarzoukView Answer on Stackoverflow
Solution 32 - Ios777QView Answer on Stackoverflow
Solution 33 - IosNaloiko EugeneView Answer on Stackoverflow
Solution 34 - IosJIANGView Answer on Stackoverflow
Solution 35 - IosFelipeView Answer on Stackoverflow