I’ve been investigating why Carthage past v0.11 is failing for us. We have pinned 0.11 but we can’t do that anymore for 3.0, because the builds that 0.11 is generating are not accepted by the App Store.
Here is a list of all the bugs around Carthage 0.15 that I have seen: https://bugzilla.mozilla.org/showdependencytree.cgi?id=1252165&hide_resolved=1 <https://bugzilla.mozilla.org/showdependencytree.cgi?id=1252165&hide_resolved=1> Now I think the only bug of significance is actually https://bugzilla.mozilla.org/show_bug.cgi?id=1252172 <https://bugzilla.mozilla.org/show_bug.cgi?id=1252172> and all the others happen as a result of that one. To deal with that bug I have filed https://github.com/Carthage/Carthage/issues/1124 <https://github.com/Carthage/Carthage/issues/1124> with the Carthage project, but I don’t know if that analysis is correct. I wrote a Python script that runs before “carthage copy-frameworks” to simply delete the .dSYM directory if it already exists, so that carthage can put it back there and strip it. This worked extremely unreliable with weird errors about those .dSYM directories already existing, even though I just deleted them. This behavior was a good hint to the following: Disabling “Parallelize Build” in Xcode make all the errors go away. Problem solved. You can do this in the Scheme editor, under the Build settings. I created a PR to do this for all our schemes: https://github.com/mozilla/firefox-ios/pull/1583 <https://github.com/mozilla/firefox-ios/pull/1583> Please give this a try on a *clean checkout* of that branch. Clean checkout is really important because Xcode caches things. Note that this is an intermediate solution until we find out what the real problem is, which in my opinion absolutely has something to do with Carthage. We lose some speed but we get working builds. S.
_______________________________________________ mobile-firefox-dev mailing list mobile-firefox-dev@mozilla.org https://mail.mozilla.org/listinfo/mobile-firefox-dev
