On Fri, Feb 20, 2015 at 6:48 PM, Brian Nicholson <[email protected]>
wrote:

Excellent :-)

Shout out to Stefan for sorting out the Travis CI and scheme issues!
>

Just to give you a quick idea of the kind of issues we can (and have) run
into when importing projects with Carthage:

Usually Carthage is used to compile frameworks and then include the
(compiled) binary frameworks in your app. When you do this, the frameworks
do not need to be signed by Carthage. Instead, at the end of building the
your application, xcode will simply sign all the embedded resources,
frameworks included. So as long as signing works for your app, it will work
for frameworks imported with Carthage.

But, because not all Carthage dependencies can be compiled to frameworks
yet, we currently include them as source. This means they become dependent
projects of our application, which in turn means that they are built *and
signed* individually as part of the build process of our app.

Now this is where it gets tricky. Because code signing on iOS can get
really tedious to get right. Small mistakes in dependent projects can turn
into issues about code signing identities, missing provisioning profiles,
etc.

For example:

If a dependent project has a team identifier set, Xcode will complain that
it cannot find signin identities of that team. It is best to set the team
to None.

If a depedenent project is configured to use a Distribution Code Signing
Identity for a Release build, Xcode will complain that such a profile is
not available. (Since we only have development profiles on our
workstations). It is best to configure both Debug and Release Build
Configurations to use the automatic "iPhone Developer" Code Signing
Identity. This will pick the right thing on your local build.

Most if this is fixable and can be reported upstream.

If you add a new dependency, ping me and I'll make sure things work
correctly on our integration (xcode server) and dogfood builders.

 S.
_______________________________________________
mobile-firefox-dev mailing list
[email protected]
https://mail.mozilla.org/listinfo/mobile-firefox-dev

Reply via email to