Bug 56635 - MT0099 : Internal error : 'can't lipo directories'
Summary: MT0099 : Internal error : 'can't lipo directories'
Status: RESOLVED FIXED
Alias: None
Product: iOS
Classification: Xamarin
Component: Tools ()
Version: XI 10.10 (d15-2)
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: 15.3
Assignee: Rolf Bjarne Kvinge [MSFT]
URL:
Depends on:
Blocks:
 
Reported: 2017-05-18 18:49 UTC by Andy
Modified: 2017-07-06 08:48 UTC (History)
8 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:


Attachments
build log (188.82 KB, text/plain)
2017-05-18 18:49 UTC, Andy
Details
A new build error for the project. (241.29 KB, text/plain)
2017-05-22 17:04 UTC, Andy
Details


Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED FIXED

Description Andy 2017-05-18 18:49:31 UTC
Created attachment 22284 [details]
build log

When adding Crashlytics to an app and app extension, it triggers "Can't lipo directories".

I forked the ios-samples repo and added the package and reference code that will make the build fail to my fork: https://github.com/zippo227/ios-samples

This one has been plaguing me for a long time. I finally compiled the xamarin-macios and have a pull request asking to add additional information to help people track down any future issue: https://github.com/xamarin/xamarin-macios/pull/2109

VS DETAILS:

Visual Studio Community 2017 for Mac
Version 7.0 (build 3146)
Installation UUID: 80b8f93e-f9ea-42b6-9ca5-f0bf2935d27e
Runtime:
	Mono 5.0.0.100 (2017-02/9667aa6) (64-bit)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 500000100

NuGet
Version: 4.0.0.2323

.NET Core
Runtime: /usr/local/share/dotnet/dotnet
SDK: /usr/local/share/dotnet/sdk/1.0.3/Sdks
MSBuild SDKs: /Library/Frameworks/Mono.framework/Versions/5.0.0/lib/mono/msbuild/15.0/bin/Sdks

Xamarin.Profiler
'/Applications/Xamarin Profiler.app' not found

Apple Developer Tools
Xcode 8.3.2 (12175)
Build 8E2002

Xamarin.iOS
Version: 10.10.0.33 (Visual Studio Community)
Hash: 3e5ac5ff
Branch: d15-2
Build date: 2017-05-05 18:11:38-0400

Xamarin.Android
Version: 7.3.0.13 (Visual Studio Community)
Android SDK: /Users/andymartin/Library/Developer/Xamarin/android-sdk-macosx
	Supported Android versions:
		2.3   (API level 10)
		4.0.3 (API level 15)
		4.3   (API level 18)
		4.4   (API level 19)
		5.1   (API level 22)
		6.0   (API level 23)
		7.0   (API level 24)
		7.1   (API level 25)

SDK Tools Version: 25.2.5
SDK Platform Tools Version: 25.0.5
SDK Build Tools Version: 25.0.3

Java SDK: /usr
java version "1.8.0_92"
Java(TM) SE Runtime Environment (build 1.8.0_92-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.92-b14, mixed mode)

Android Designer EPL code available here:
https://github.com/xamarin/AndroidDesigner.EPL

Xamarin.Mac
Version: 3.4.0.33 (Visual Studio Community)

Xamarin Inspector
Version: 1.2.2
Hash: b71b035
Branch: d15-1
Build date: Fri, 21 Apr 2017 17:57:12 GMT

Build Information
Release ID: 700003146
Git revision: 7553fda2e327d15807298d444007896e5b975dba
Build date: 2017-05-09 12:12:36-04
Xamarin addins: c3d580752be79fc902422f1d55d1cdc2d8b98799
Build lane: monodevelop-lion-d15-2

Operating System
Mac OS X 10.12.4
Darwin 16.5.0 Darwin Kernel Version 16.5.0
    Fri Mar  3 16:52:33 PST 2017
    root:xnu-3789.51.2~3/RELEASE_X86_64 x86_64
Comment 1 Sebastien Pouliot 2017-05-18 20:03:23 UTC
error MT0099 : Internal error : 'can't lipo directories'. Please file a bug report with a test case (http://bugzilla.xamarin.com).
Comment 2 Rolf Bjarne Kvinge [MSFT] 2017-05-19 08:26:47 UTC
master: https://github.com/xamarin/xamarin-macios/pull/2112
Comment 4 Andy 2017-05-19 20:56:45 UTC
That was a quick turnaround! Nice job @Rofl However, I did a make all install with the latest master, and now my IceCreamBuilder example has this error:

/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/iOS/Xamarin.iOS.Common.targets(1516,3): error MSB6006: "ditto" exited with code 1.
Comment 5 Rolf Bjarne Kvinge [MSFT] 2017-05-22 07:30:07 UTC
@Andy, that's new, your test project worked for me. Can you attach the complete build log?
Comment 6 Andy 2017-05-22 17:04:35 UTC
Created attachment 22359 [details]
A new build error for the project.

Now when building I'm getting a new error. This log was requested by @Rolf
Comment 7 Rolf Bjarne Kvinge [MSFT] 2017-05-23 06:12:28 UTC
@Andy, that's a different bug, and I've reported is as bug #56748. Workaround: enable (or disable) device-specific builds in all projects.
Comment 8 Andy 2017-05-23 13:46:58 UTC
Sure, that makes sense. I couldn't tell if they were related. I'm CC'd on the new one.
Comment 9 Songtive Team 2017-06-02 14:34:20 UTC
@Rolf I've just encountered the same issue - is it going to release this fix for Alpha/Stable channel?
Comment 10 Rolf Bjarne Kvinge [MSFT] 2017-06-02 14:36:40 UTC
@Songtive, yes, we'll fix this in a later alpha release (the bug doesn't exist in the current stable release).
Comment 11 Songtive Team 2017-06-02 14:39:23 UTC
I experience the bug with the current stable version. Once I try to add Extension with the library which contains Crashalytics I get the error Can't lipo directories. 


Xamarin Studio Enterprise
Version 6.3 (build 864)
Installation UUID: 73dcb3fb-2412-4ed6-bbfc-176ee820e6ab
Runtime:
	Mono 5.0.1.1 (2017-02/5077205) (64-bit)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 500010001

NuGet
Version: 3.5.0.0

Xamarin.Profiler
Version: 0.38.0
Location: /Applications/Xamarin Profiler.app/Contents/MacOS/Xamarin Profiler

Apple Developer Tools
Xcode 8.3.2 (12175)
Build 8E2002

Xamarin.iOS
Version: 10.10.0.36 (Visual Studio Enterprise)
Hash: d2270eec
Branch: d15-2
Build date: 2017-05-22 16:30:53-0400

Xamarin.Android
Version: 7.3.1.2 (Visual Studio Enterprise)
Android SDK: /Users/sergeybogdanov/Library/Android/sdk
	Supported Android versions:
		2.3   (API level 10)
		4.0.3 (API level 15)
		4.1   (API level 16)
		4.4   (API level 19)
		5.1   (API level 22)
		6.0   (API level 23)
		7.0   (API level 24)
		7.1   (API level 25)

SDK Tools Version: 26.0.2
SDK Platform Tools Version: 25.0.6
SDK Build Tools Version: 25.0.2

Java SDK: /Library/Java/JavaVirtualMachines/jdk1.8.0_45.jdk/Contents/Home
java version "1.8.0_45"
Java(TM) SE Runtime Environment (build 1.8.0_45-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.45-b02, mixed mode)

Android Designer EPL code available here:
https://github.com/xamarin/AndroidDesigner.EPL

Xamarin.Mac
Version: 3.4.0.36 (Visual Studio Enterprise)

Xamarin Inspector
Not Installed

Build Information
Release ID: 603000864
Git revision: 6c2f6737278ccc3e81e12276d49c0d92f975f189
Build date: 2017-04-24 11:26:01-04
Xamarin addins: d8d46e577d8507c35260ce9d73df3c33415bb214
Build lane: monodevelop-lion-d15-1

Operating System
Mac OS X 10.12.4
Darwin desmbp.local 16.5.0 Darwin Kernel Version 16.5.0
    Fri Mar  3 16:52:33 PST 2017
    root:xnu-3789.51.2~3/RELEASE_X86_64 x86_64
Comment 12 Andy 2017-06-02 14:40:25 UTC
It does affect the current stable release.
Comment 13 Rolf Bjarne Kvinge [MSFT] 2017-06-02 14:44:43 UTC
@Songtive, you're right, I got confused with a different bug.

You can add "--nodevcodeshare" to the additional mtouch arguments in both the main project and the extension project, and it should build fine.
Comment 14 Songtive Team 2017-06-02 14:52:48 UTC
Works perfectly. Thanks!
Comment 15 Songtive Team 2017-06-05 19:16:07 UTC
@Rolf, I've noticed one more thing. If a library shared between application and extension doesn't have Crashalytics then it works perfectly. Once I try to add Crashalytics to the library then I still get the error "can't lipo directories" and "--nodevcodeshare" doesn't help to resolve it. Removing Crashalytics (v1.4) from library project helps to resolve the issue.
Comment 16 Tuyen Duc Vu 2017-06-29 11:16:32 UTC
I also faced this issue when trying to link some DLLs which should normally be linked :(.
Comment 17 Manuel de la Peña [MSFT] 2017-07-06 08:48:23 UTC
*** Bug 57117 has been marked as a duplicate of this bug. ***