Skip to content
This repository has been archived by the owner on Nov 2, 2019. It is now read-only.

Building with carthage results in 2 Bolts.framework being built? #255

Closed
5 tasks done
Nonnus opened this issue Aug 14, 2018 · 21 comments
Closed
5 tasks done

Building with carthage results in 2 Bolts.framework being built? #255

Nonnus opened this issue Aug 14, 2018 · 21 comments

Comments

@Nonnus
Copy link

Nonnus commented Aug 14, 2018

Facebook Swift SDK Issue

Checklist

Environment

When doing a clean build using carthage we end up with 2 Bolts frameworks, one in build folder and another in build/static folder (wich i assume it a static version of the framework):
this feels wrong and seems to be undocumented, is it an expected behavior?
wich of them should we include in our projects?

  • Xcode Version: 9.4.1
  • Swift Version: 4.1.2
  • Installation Platform & Verison: Carthage version 0.30.1

Issue Details

  • Bugs: Please fill out all the sections below
  • Feature Request: Please fill out the first two sections below, remove the rest of the sections, AND give your issue the title: Feature Request: [name of your feature request]

Goals

Build swift facebook sdk using carthage

Expected Results

End up with only one build Bolts framework

Actual Results

Ended up with 2 Bolts frameworks being built in different folders:
screen shot 2018-08-14 at 10 45 43

Steps to Reproduce

1 Create blank project
2 Add Cartfile with github "facebook/Facebook-SDK-Swift"
3 run carthage update --platform ios

Code Samples & Details

FB-Test.zip

@vitorhugomagalhaes
Copy link

@Nonnus It seems that one is the dynamic and the other the static one. Not sure if this is an issue.

@Nonnus
Copy link
Author

Nonnus commented Aug 22, 2018

i had that notion as well (even mentioned it on my initial issue description)
but it would still be nice to have more info about it,
in the integration docs there is no mention of this aspect,
nor any instructions about adding the dynamic vs static version of the framework as there are slight differences (mainly skipping the copy-frameworks build phase for the static version of the framework)

@vitorhugomagalhaes
Copy link

True. Moreover I'd like to see some "standardisation" across different carthage packages to make this more clear for everyone.

@codytwinton
Copy link
Contributor

Thanks for reporting this issue. I'm doing some work with the underlying Objective-C SDK right now, but I'll do my best to address this asap.

@Nonnus
Copy link
Author

Nonnus commented Aug 22, 2018

@codytwinton i assumed so, this is why i did not even @mentioned you not to disturb ;)

@codytwinton
Copy link
Contributor

@Nonnus - Great news, it appears that a similar pull request on the Bolts framework was approved and merged. This might be resolved with BoltsFramework/Bolts-ObjC#324.

@Nonnus
Copy link
Author

Nonnus commented Sep 26, 2018

@codytwinton great news! I suppose a new release will be generated so that it can be automatically picked up when building facebook-sdk-swift

@codytwinton
Copy link
Contributor

facebook-objc-sdk master branch now targets the latest version of Bolts.

@Nonnus
Copy link
Author

Nonnus commented Sep 27, 2018

@codytwinton testing right now

@codytwinton
Copy link
Contributor

@Nonnus let me know.

@Nonnus
Copy link
Author

Nonnus commented Sep 27, 2018

@codytwinton I assume it requires carthage to be updated to 0.31.0?
I still had 0.30.1 and running carthage update Facebook-SDK-Swift --platform ios failed:
screenshot 2018-09-28 at 00 38 02

@Nonnus
Copy link
Author

Nonnus commented Sep 27, 2018

@codytwinton same with carthage 0.31.0:
screenshot 2018-09-28 at 00 44 10

here is the build log:
carthage-xcodebuild.58iRaH.log

@codytwinton
Copy link
Contributor

@Nonnus - I believe so, yes.

@codytwinton
Copy link
Contributor

@Nonnus - damn, ok. This appears to be an issue with Xcode 10 still, but I believe I might know the root cause. I'll check this out and confirm shortly.

@Nonnus
Copy link
Author

Nonnus commented Sep 27, 2018

@codytwinton I updated my previous post with my build log, It might help:
screenshot 2018-09-28 at 00 47 35

@codytwinton
Copy link
Contributor

Can you update your Cartfile to target the master branch for the facebook-objc-sdk?

@Nonnus
Copy link
Author

Nonnus commented Sep 27, 2018

running it now (I was actually not including it on the cartfile, nor Bolts, only Facebook-SDK-Swift, I assume this should be fine once the setup is fixed?)
I was going to tell you that I noticed on my Cartfile.resolved that checked out Bolts was still on 1.9.0

@codytwinton
Copy link
Contributor

Yes, once everything is resolved and all cartfile's are updated properly, this will be just fine.

@Nonnus
Copy link
Author

Nonnus commented Sep 27, 2018

not, it failed again, I am afraid :(
I am a bit suspicious about this: facebook-objc-sdk is now at commit 79caaaf56ce3eb00a0a7852361d4c250459f2e43 (latest master commit) but checkout Bolts on my Cartfile.resolved is still 1.9.0:
screenshot 2018-09-28 at 00 57 08

build log:
carthage-xcodebuild.lkKXNy.log

@codytwinton
Copy link
Contributor

Also could be related to this:

facebook/facebook-ios-sdk#914 (comment)

@codytwinton
Copy link
Contributor

This should be resolved with version 0.5.0

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants