Lipo Error: can't open input file

I

4

6

I'm getting this error:

/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin/lipo: can't open input file: /Users/snowcrash/Library/Developer/Xcode/DerivedData/MyApp-awldrudjpictkjfutpthiwoocing/Build/Intermediates/ArchiveIntermediates/MyApp/IntermediateBuildFilesPath/MyApp.build/Distribution-iphoneos/MyApp.build/Objects-normal/armv7/MyApp (No such file or directory)

Any suggestions?

Incorporeal answered 22/7, 2013 at 15:15 Comment(7)

Why is lipo being run? – Ondrea 22/7, 2013 at 15:19

Dunno. Is it not required then? – Incorporeal 22/7, 2013 at 15:22

It's used to combine multi-arch binaries into a single binary. I guess it depends on whether you support multiple arches. Has it ever worked? – Ondrea 22/7, 2013 at 15:24

Yes. Currently, building for armv7 and armv7s. – Incorporeal 22/7, 2013 at 15:36

Have you tried the usual, Clean project, delete derived data and snapshots, and the relaunching? Generally that fixes these sort of 'stuck' XCode issues. – Iceman 22/7, 2013 at 15:42

Hmm... yes, several times. However, this last time fixed it! – Incorporeal 22/7, 2013 at 15:49

This happened to me because I'm using cocoapods and the Pods project in the workspace had a different setting for "Build Active Architecture Only" than my main project (YES and NO respectively). When I set both to "NO" I was able to build and run on my device. – Octahedron 27/2, 2014 at 1:35

T

6

Go to Project target-> Build setting-> Build Active Architecture only and set this Build Active Architecture only to YES. And it's working fine now..

Thelmathem answered 31/1, 2014 at 10:59 Comment(0)

F

2

I also got the same problem. I was using cocoapods, and some other person committed the code after adding new pods with different cocoapods version. you need to clean the project again installing the pods and run the xcode.

Frawley answered 27/10, 2015 at 17:18 Comment(0)

A

0

In my case, it was a stale library. I had -xxxunusedlibrary in 'Other linker flags' in Build Settings.

The library had been removed but the settings didn't clear automatically.

Amylum answered 12/1, 2017 at 3:59 Comment(0)

R

0

I have encountered this problem because command can't find the file generated by build. Please check whether your static library path is consistent with the command file path.

Rockbottom answered 15/1, 2021 at 10:23 Comment(0)

Recommended topics

Hot tags