Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

iOS

Apple Mach-O Linker Error in XCode, after update to IOS 7.1 and XCode 5.1

This is weird problem, I recently updated my iPhone to IOS 7.1 (I wish I waited), because of that Xcode said it too needed to be updated. Did so, but now I'm getting Mach-O linker errors. Reading the description, it said that there was an ignored file the DropboxSDK (from the DropboxSDK.framworks) claiming that it is missing a required architecture arm64 in the file. This is a new one for me, I'm still very new to objective-c programming and XCode so any help would be welcome.

5 Answers

After searching for awhile, it apparently for me was arm64 in my valid architectures. After I removed that the errors went away.

Patrick Donahue
Patrick Donahue
9,523 Points

Try this webanswer.

I have gotten the Mach-O error before when adding Crashlytics to a project. It seems to be an issue with the framework being misconfigured. But I could be wrong.

Tim Dai
Tim Dai
1,679 Points

Thanks Patrick! I tried it but it didn't work for my case. Hi Allan, I just updated my iPhone to 7.1 too. Now I'm having the same issue - " Mach-O Linker Error". I will keep looking for solutions, and try different approaches. keep you posted if i find anything useful. Did you use PhoneGap or similar software? Could that be the causes?

Patrick Donahue
Patrick Donahue
9,523 Points

Can you post the exact Mach-O Linker Errors you are getting?

Patrick Donahue
Patrick Donahue
9,523 Points

I figured it out - you have to set the version of the app to the version that is on the device.

Matthew Chess
Matthew Chess
13,860 Points

I ran into this issue and needed to double check the frameworks that I imported matched the ones in the video. I noticed that the current parse documentation they say to import libz.dylib however in the video they import the 1.1.3 file.