New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Xcode 8.1 support #6791

Closed
heyzooi opened this Issue Oct 28, 2016 · 77 comments

Comments

Projects
None yet
@heyzooi

heyzooi commented Oct 28, 2016

Please add Xcode 8.1 support

osx_image: xcode8.1

@seivan

This comment has been minimized.

Show comment
Hide comment
@seivan

seivan Oct 31, 2016

One of the reasons we pay for Travis is because we're expecting you to be ahead of the curve. However, I am not sure that's an unreasonable request.

seivan commented Oct 31, 2016

One of the reasons we pay for Travis is because we're expecting you to be ahead of the curve. However, I am not sure that's an unreasonable request.

@bielikb

This comment has been minimized.

Show comment
Hide comment
@bielikb

bielikb Oct 31, 2016

Travis is always behind :/

bielikb commented Oct 31, 2016

Travis is always behind :/

@joshk

This comment has been minimized.

Show comment
Hide comment
@joshk

joshk Oct 31, 2016

Member

Thanks for the feedback.

We usually aim for a 24-48 hour turn around for new Xcode versions, but due to some team members being out of the office last week, this has been a little delayed.

We will look into this request later this week and see what we can do.

Have an awesome day!

Member

joshk commented Oct 31, 2016

Thanks for the feedback.

We usually aim for a 24-48 hour turn around for new Xcode versions, but due to some team members being out of the office last week, this has been a little delayed.

We will look into this request later this week and see what we can do.

Have an awesome day!

@stefanhp

This comment has been minimized.

Show comment
Hide comment
@stefanhp

stefanhp Nov 1, 2016

It would also be nice to have it on macOS 10.12 (Sierra).

stefanhp commented Nov 1, 2016

It would also be nice to have it on macOS 10.12 (Sierra).

@NachoSoto

This comment has been minimized.

Show comment
Hide comment
@NachoSoto

NachoSoto Nov 3, 2016

Any updates on this @joshk?

NachoSoto commented Nov 3, 2016

Any updates on this @joshk?

@BanzaiMan

This comment has been minimized.

Show comment
Hide comment
@BanzaiMan

BanzaiMan Nov 3, 2016

Member

Sorry for the delay. We are working on it.

Member

BanzaiMan commented Nov 3, 2016

Sorry for the delay. We are working on it.

@bielikb

This comment has been minimized.

Show comment
Hide comment
@bielikb

bielikb Nov 7, 2016

we already resigned to wait for this update as we're in the release week of our product, thus running important stuff using other services. hopefully Travis will be on track with latest Xcode update next time

bielikb commented Nov 7, 2016

we already resigned to wait for this update as we're in the release week of our product, thus running important stuff using other services. hopefully Travis will be on track with latest Xcode update next time

@rikvdbrule

This comment has been minimized.

Show comment
Hide comment
@rikvdbrule

rikvdbrule Nov 10, 2016

Please update soon, Xcode 8.1 fixes a compiler issue that is critical to distribute our app.

rikvdbrule commented Nov 10, 2016

Please update soon, Xcode 8.1 fixes a compiler issue that is critical to distribute our app.

@oleksandr-yefremov

This comment has been minimized.

Show comment
Hide comment
@oleksandr-yefremov

oleksandr-yefremov Nov 10, 2016

heyzooi opened this Issue 14 days ago

BanzaiMan commented 7 days ago
Sorry for the delay. We are working on it.

C'mon guys! If you have some reasonable delays, please communicate it ASAP. We rely on availability of current stable Apple APIs. Yes, Apple is rolling out language and tools versions way too often, but if you can't keep up we need to have a backup plan (Jenkins in a basement). Right now I personally can't prepare for release and have to either introduce Jenkins and set it up from scratch or wait until current issue is unblocked 😞

oleksandr-yefremov commented Nov 10, 2016

heyzooi opened this Issue 14 days ago

BanzaiMan commented 7 days ago
Sorry for the delay. We are working on it.

C'mon guys! If you have some reasonable delays, please communicate it ASAP. We rely on availability of current stable Apple APIs. Yes, Apple is rolling out language and tools versions way too often, but if you can't keep up we need to have a backup plan (Jenkins in a basement). Right now I personally can't prepare for release and have to either introduce Jenkins and set it up from scratch or wait until current issue is unblocked 😞

@brianmichel

This comment has been minimized.

Show comment
Hide comment
@brianmichel

brianmichel Nov 10, 2016

Any movement here? Would love to use the same build environment in Travis that we are on our locals.

brianmichel commented Nov 10, 2016

Any movement here? Would love to use the same build environment in Travis that we are on our locals.

@solarce

This comment has been minimized.

Show comment
Hide comment
@solarce

solarce Nov 11, 2016

Firstly, I want to apologize for both the delay in having support for Xcode 8.1 and the lack of communication for the last few days.

Getting support for Xcode 8.1 has been delayed while we've been working to get macOS 10.12 setup. This process has required us to build a new base OS image from scratch and unfortunately, we've run into more complications with getting 10.12 ready than we expected.

However, we're in the final stages of integration testing and hope to have the image ready for testing by Mon/Tue next week. Right now we think we'll initially promote it with a separate osx_image: value at first and ask folks who are watching this thread to try it out, before we promote it to replace xcode8

Again, I am sorry for the delays and lack of sufficient updates along the way. I'll post an update on where we are by the EOD, Mon, Nov 14th.

solarce commented Nov 11, 2016

Firstly, I want to apologize for both the delay in having support for Xcode 8.1 and the lack of communication for the last few days.

Getting support for Xcode 8.1 has been delayed while we've been working to get macOS 10.12 setup. This process has required us to build a new base OS image from scratch and unfortunately, we've run into more complications with getting 10.12 ready than we expected.

However, we're in the final stages of integration testing and hope to have the image ready for testing by Mon/Tue next week. Right now we think we'll initially promote it with a separate osx_image: value at first and ask folks who are watching this thread to try it out, before we promote it to replace xcode8

Again, I am sorry for the delays and lack of sufficient updates along the way. I'll post an update on where we are by the EOD, Mon, Nov 14th.

@solarce

This comment has been minimized.

Show comment
Hide comment
@solarce

solarce Nov 11, 2016

We have a 10.12/Xcode 8.1 image ready for some testing, you can try it out with osx_image: xcode8.1sneakpeek. Please let us know how it works for you. We'll determine our promotion plan to make it the default xcode8 image early next week

solarce commented Nov 11, 2016

We have a 10.12/Xcode 8.1 image ready for some testing, you can try it out with osx_image: xcode8.1sneakpeek. Please let us know how it works for you. We'll determine our promotion plan to make it the default xcode8 image early next week

@aaronbrethorst

This comment has been minimized.

Show comment
Hide comment
@aaronbrethorst

aaronbrethorst Nov 11, 2016

https://travis-ci.org/OneBusAway/onebusaway-iphone/builds/175201230

2016-11-11 22:19:25.674 xcodebuild[1566:5939] Error Domain=IDETestOperationsObserverErrorDomain Code=3 "Canceling tests due to timeout in Checking test manager availability... If you believe this error represents a bug, please attach the log file at /Users/travis/Library/Developer/Xcode/DerivedData/org.onebusaway.iphone-gyziilhhwnahyrdtswtcuvzaxxtr/Logs/Test/D8FC026B-1E9C-4F43-B9FE-0F2D988C43FD/Session-OneBusAwayTests-2016-11-11_221720-HjdFR7.log" UserInfo={NSLocalizedDescription=Canceling tests due to timeout in Checking test manager availability... If you believe this error represents a bug, please attach the log file at /Users/travis/Library/Developer/Xcode/DerivedData/org.onebusaway.iphone-gyziilhhwnahyrdtswtcuvzaxxtr/Logs/Test/D8FC026B-1E9C-4F43-B9FE-0F2D988C43FD/Session-OneBusAwayTests-2016-11-11_221720-HjdFR7.log}

aaronbrethorst commented Nov 11, 2016

https://travis-ci.org/OneBusAway/onebusaway-iphone/builds/175201230

2016-11-11 22:19:25.674 xcodebuild[1566:5939] Error Domain=IDETestOperationsObserverErrorDomain Code=3 "Canceling tests due to timeout in Checking test manager availability... If you believe this error represents a bug, please attach the log file at /Users/travis/Library/Developer/Xcode/DerivedData/org.onebusaway.iphone-gyziilhhwnahyrdtswtcuvzaxxtr/Logs/Test/D8FC026B-1E9C-4F43-B9FE-0F2D988C43FD/Session-OneBusAwayTests-2016-11-11_221720-HjdFR7.log" UserInfo={NSLocalizedDescription=Canceling tests due to timeout in Checking test manager availability... If you believe this error represents a bug, please attach the log file at /Users/travis/Library/Developer/Xcode/DerivedData/org.onebusaway.iphone-gyziilhhwnahyrdtswtcuvzaxxtr/Logs/Test/D8FC026B-1E9C-4F43-B9FE-0F2D988C43FD/Session-OneBusAwayTests-2016-11-11_221720-HjdFR7.log}
@andybfp

This comment has been minimized.

Show comment
Hide comment
@andybfp

andybfp Nov 11, 2016

Config includes:
osx_image: xcode8.1sneakpeek
"rvm": "2.2.2",

Build Log results:
$ rvm use 2.2.2 --install --binary --fuzzy
ruby-2.2.2 is not installed - installing.
Searching for binary rubies, this might take some time.
Requested binary installation but no rubies are available to download, consider skipping --binary flag.
Gemset '' does not exist, 'rvm ruby-2.2.2 do rvm gemset create ' first, or append '--create'.
The command "rvm use 2.2.2 --install --binary --fuzzy" failed and exited with 2 during .

andybfp commented Nov 11, 2016

Config includes:
osx_image: xcode8.1sneakpeek
"rvm": "2.2.2",

Build Log results:
$ rvm use 2.2.2 --install --binary --fuzzy
ruby-2.2.2 is not installed - installing.
Searching for binary rubies, this might take some time.
Requested binary installation but no rubies are available to download, consider skipping --binary flag.
Gemset '' does not exist, 'rvm ruby-2.2.2 do rvm gemset create ' first, or append '--create'.
The command "rvm use 2.2.2 --install --binary --fuzzy" failed and exited with 2 during .

@seivan

This comment has been minimized.

Show comment
Hide comment
@seivan

seivan Nov 12, 2016

Out of curiosity what's the point of the "sneakpeek" suffix, it seems redundant given the fact that it isn't a documented feature and forces people to hit back the .yml file for modification as soon as the "sneakpeek" is over.

I had the same issue as @andybfp

16.19s$ rvm use 2.3.1 --install --binary --fuzzy
ruby-2.3.1 is not installed - installing.
Searching for binary rubies, this might take some time.
Requested binary installation but no rubies are available to download, consider skipping --binary flag.
Gemset '' does not exist, 'rvm ruby-2.3.1 do rvm gemset create ' first, or append '--create'.
The command "rvm use 2.3.1 --install --binary --fuzzy" failed and exited with 2 during .

seivan commented Nov 12, 2016

Out of curiosity what's the point of the "sneakpeek" suffix, it seems redundant given the fact that it isn't a documented feature and forces people to hit back the .yml file for modification as soon as the "sneakpeek" is over.

I had the same issue as @andybfp

16.19s$ rvm use 2.3.1 --install --binary --fuzzy
ruby-2.3.1 is not installed - installing.
Searching for binary rubies, this might take some time.
Requested binary installation but no rubies are available to download, consider skipping --binary flag.
Gemset '' does not exist, 'rvm ruby-2.3.1 do rvm gemset create ' first, or append '--create'.
The command "rvm use 2.3.1 --install --binary --fuzzy" failed and exited with 2 during .
@solarce

This comment has been minimized.

Show comment
Hide comment
@solarce

solarce Nov 12, 2016

Once we are happy with this 8.1 image it will replace our xcode8 image.
We do not plan to support 8.0 and 8.1 side by side.

The rvm thing is due to a lack of a prebuilt binary version of 2.2.2 for
10.12. We can look into publishing one next week

Brandon Burton

On November 11, 2016 at 18:13:55, Seivan Heidari (notifications@github.com)
wrote:

Out of curiosity what's the point of the "sneakpeek" suffix, it seems
redundant given the fact that it isn't a documented feature and forces
people to hit back the .yml file for modification as soon as the
"sneakpeek" is over.

I had the same issue as @andybfp https://github.com/andybfp

16.19s$ rvm use 2.3.1 --install --binary --fuzzy
ruby-2.3.1 is not installed - installing.
Searching for binary rubies, this might take some time.
Requested binary installation but no rubies are available to download, consider skipping --binary flag.
Gemset '' does not exist, 'rvm ruby-2.3.1 do rvm gemset create ' first, or append '--create'.
The command "rvm use 2.3.1 --install --binary --fuzzy" failed and exited with 2 during .


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#6791 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAlvMDpzVtOKdUEB4tvlkzyqNlXI9xAks5q9SDjgaJpZM4Ki-Ja
.

solarce commented Nov 12, 2016

Once we are happy with this 8.1 image it will replace our xcode8 image.
We do not plan to support 8.0 and 8.1 side by side.

The rvm thing is due to a lack of a prebuilt binary version of 2.2.2 for
10.12. We can look into publishing one next week

Brandon Burton

On November 11, 2016 at 18:13:55, Seivan Heidari (notifications@github.com)
wrote:

Out of curiosity what's the point of the "sneakpeek" suffix, it seems
redundant given the fact that it isn't a documented feature and forces
people to hit back the .yml file for modification as soon as the
"sneakpeek" is over.

I had the same issue as @andybfp https://github.com/andybfp

16.19s$ rvm use 2.3.1 --install --binary --fuzzy
ruby-2.3.1 is not installed - installing.
Searching for binary rubies, this might take some time.
Requested binary installation but no rubies are available to download, consider skipping --binary flag.
Gemset '' does not exist, 'rvm ruby-2.3.1 do rvm gemset create ' first, or append '--create'.
The command "rvm use 2.3.1 --install --binary --fuzzy" failed and exited with 2 during .


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#6791 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAlvMDpzVtOKdUEB4tvlkzyqNlXI9xAks5q9SDjgaJpZM4Ki-Ja
.

@stefanhp

This comment has been minimized.

Show comment
Hide comment
@stefanhp

stefanhp Nov 12, 2016

This 10.12/Xcode 8.1 image works for me.
👍

stefanhp commented Nov 12, 2016

This 10.12/Xcode 8.1 image works for me.
👍

@Ben-G Ben-G referenced this issue Nov 12, 2016

Merged

Release 3.0.0 #166

@iforvert

This comment has been minimized.

Show comment
Hide comment
@cepages

This comment has been minimized.

Show comment
Hide comment
@cepages

cepages Nov 14, 2016

@stefanhp are you using osx_image: xcode8.1sneakpeek or osx_image: xcode8

cepages commented Nov 14, 2016

@stefanhp are you using osx_image: xcode8.1sneakpeek or osx_image: xcode8

@HazAT

This comment has been minimized.

Show comment
Hide comment
@HazAT

HazAT Nov 29, 2016

I just wanted to join the conversation here ...

We are still having troubles completing our build, its stuck in the signing phase ...
We tried everything described earlier in this thread (changing the security commands) but its still stuck.
Right now its not a major issue because the build works without any issues on xcode8.
I also talked with @cotsog via mail already about this ;)

I am curious if its just us ...

HazAT commented Nov 29, 2016

I just wanted to join the conversation here ...

We are still having troubles completing our build, its stuck in the signing phase ...
We tried everything described earlier in this thread (changing the security commands) but its still stuck.
Right now its not a major issue because the build works without any issues on xcode8.
I also talked with @cotsog via mail already about this ;)

I am curious if its just us ...

@rakaramos

This comment has been minimized.

Show comment
Hide comment
@rakaramos

rakaramos Nov 29, 2016

@HazAT we are having issues here because Xcode 8 has issues with storyboard/xib compilations.
E.g: Building on Xcode 8, we have a dark overlay being added to the screen. On Xcode 8.1, the issue is not there (Weird right?)

rakaramos commented Nov 29, 2016

@HazAT we are having issues here because Xcode 8 has issues with storyboard/xib compilations.
E.g: Building on Xcode 8, we have a dark overlay being added to the screen. On Xcode 8.1, the issue is not there (Weird right?)

@sbandol

This comment has been minimized.

Show comment
Hide comment
@sbandol

sbandol Nov 29, 2016

We also have issues with Xcode8 image (mostly UI as @rakaramos says).
Xcode8.1 image still not working for us, so we are building manually for now.

sbandol commented Nov 29, 2016

We also have issues with Xcode8 image (mostly UI as @rakaramos says).
Xcode8.1 image still not working for us, so we are building manually for now.

@cepages

This comment has been minimized.

Show comment
Hide comment
@cepages

cepages Nov 29, 2016

@cotsog yeah, the signing is made by fastlane/match

cepages commented Nov 29, 2016

@cotsog yeah, the signing is made by fastlane/match

@rakaramos

This comment has been minimized.

Show comment
Hide comment
@rakaramos

rakaramos Nov 29, 2016

Guys, just figured that out. It seems that we were missing the codesign application id

security set-key-partition-list -S apple-tool:,apple:,codesign: -s -k keychainPass keychainName

I'm using keychainName.keychain (added the extension .keychain)

rakaramos commented Nov 29, 2016

Guys, just figured that out. It seems that we were missing the codesign application id

security set-key-partition-list -S apple-tool:,apple:,codesign: -s -k keychainPass keychainName

I'm using keychainName.keychain (added the extension .keychain)

@markobyte

This comment has been minimized.

Show comment
Hide comment
@markobyte

markobyte Nov 29, 2016

Can confirm that the solution from @rakaramos works, just successfully deployed a new app update.

markobyte commented Nov 29, 2016

Can confirm that the solution from @rakaramos works, just successfully deployed a new app update.

@vegidio

This comment has been minimized.

Show comment
Hide comment
@vegidio

vegidio Nov 30, 2016

@rakaramos Are there any specific values for keychainPass and keychainPass? I'm using Fastlane to sign my application so I'm not sure what values I should use there.

vegidio commented Nov 30, 2016

@rakaramos Are there any specific values for keychainPass and keychainPass? I'm using Fastlane to sign my application so I'm not sure what values I should use there.

@markobyte

This comment has been minimized.

Show comment
Hide comment
@markobyte

markobyte Nov 30, 2016

@vegidio Use the same values as for when you create a keychain: security create-keychain -p [keychainPass] [keychainName]. set-key-partition-list works without the -p though.

markobyte commented Nov 30, 2016

@vegidio Use the same values as for when you create a keychain: security create-keychain -p [keychainPass] [keychainName]. set-key-partition-list works without the -p though.

@HazAT

This comment has been minimized.

Show comment
Hide comment
@HazAT

HazAT Dec 1, 2016

For everyone still having troubles signing the app with fastlane / match
@cotsog Pointed out that you apparently have to create a keychain with password in order to make the signing with match work

Adding this to the Fastfile did the trick

create_keychain(
      name: ENV["MATCH_KEYCHAIN_NAME"],
      password: ENV["MATCH_KEYCHAIN_PASSWORD"],
      timeout: 3600
)

Thx @cotsog 🎉

HazAT commented Dec 1, 2016

For everyone still having troubles signing the app with fastlane / match
@cotsog Pointed out that you apparently have to create a keychain with password in order to make the signing with match work

Adding this to the Fastfile did the trick

create_keychain(
      name: ENV["MATCH_KEYCHAIN_NAME"],
      password: ENV["MATCH_KEYCHAIN_PASSWORD"],
      timeout: 3600
)

Thx @cotsog 🎉

@Rusik

This comment has been minimized.

Show comment
Hide comment
@Rusik

Rusik Dec 2, 2016

Thanks @rakaramos and @bielikb! Everything working now for me

Rusik commented Dec 2, 2016

Thanks @rakaramos and @bielikb! Everything working now for me

@Sega-Zero

This comment has been minimized.

Show comment
Hide comment
@Sega-Zero

Sega-Zero Dec 5, 2016

thx to @HazAT, got everything working - forgot to specify MATCH_KEYCHAIN_NAME variable, had only KEYCHAIN_NAME specified.
the default login.keychain seemed to be created without the password, so security set-key-partition-list -S apple-tool:,apple:,codesign: -s -k keychainPass keychainName always fails. @joshk FYI

Sega-Zero commented Dec 5, 2016

thx to @HazAT, got everything working - forgot to specify MATCH_KEYCHAIN_NAME variable, had only KEYCHAIN_NAME specified.
the default login.keychain seemed to be created without the password, so security set-key-partition-list -S apple-tool:,apple:,codesign: -s -k keychainPass keychainName always fails. @joshk FYI

@cotsog

This comment has been minimized.

Show comment
Hide comment
@cotsog

cotsog Dec 7, 2016

@sbandol: sorry for the delay but could you send an e-mail to support [at] travis-ci [dot] com with the name of your repository and a link/URL to a build log showing your latest attempt to run your build on our Xcode 8.1 image i.e. osx_image: xcode8.1. Thanks!

cotsog commented Dec 7, 2016

@sbandol: sorry for the delay but could you send an e-mail to support [at] travis-ci [dot] com with the name of your repository and a link/URL to a build log showing your latest attempt to run your build on our Xcode 8.1 image i.e. osx_image: xcode8.1. Thanks!

@sbandol

This comment has been minimized.

Show comment
Hide comment
@sbandol

sbandol Dec 7, 2016

Thanks @cotsog.
Following @HazAT recommendation got it working with:

    create_keychain(
      name: ENV["MATCH_KEYCHAIN_NAME"],
      password: ENV["MATCH_PASSWORD"],
      default_keychain: true,
      unlock: true,
      timeout: 3600,
      add_to_search_list: true
    )
    match(
      type: "adhoc",
      keychain_name: ENV["MATCH_KEYCHAIN_NAME"],
      keychain_password: ENV["MATCH_PASSWORD"],
      readonly: true
    )

sbandol commented Dec 7, 2016

Thanks @cotsog.
Following @HazAT recommendation got it working with:

    create_keychain(
      name: ENV["MATCH_KEYCHAIN_NAME"],
      password: ENV["MATCH_PASSWORD"],
      default_keychain: true,
      unlock: true,
      timeout: 3600,
      add_to_search_list: true
    )
    match(
      type: "adhoc",
      keychain_name: ENV["MATCH_KEYCHAIN_NAME"],
      keychain_password: ENV["MATCH_PASSWORD"],
      readonly: true
    )
@codeOfRobin

This comment has been minimized.

Show comment
Hide comment
@codeOfRobin

codeOfRobin Jan 2, 2017

@sbandol it's still failing for me after including your code in my Fastfile.

codeOfRobin commented Jan 2, 2017

@sbandol it's still failing for me after including your code in my Fastfile.

@cotsog

This comment has been minimized.

Show comment
Hide comment
@cotsog

cotsog Jan 11, 2017

@codeOfRobin: sorry for the delay of my reply but if you are still having problems, could you send us an e-mail to support [at] travis-ci [dot] com with the name of your repository and a link/URL to a build log showing your latest attempt on travis-ci.org or travis-ci.com? Thanks!

cotsog commented Jan 11, 2017

@codeOfRobin: sorry for the delay of my reply but if you are still having problems, could you send us an e-mail to support [at] travis-ci [dot] com with the name of your repository and a link/URL to a build log showing your latest attempt on travis-ci.org or travis-ci.com? Thanks!

@codeOfRobin

This comment has been minimized.

Show comment
Hide comment
@codeOfRobin

codeOfRobin commented Jan 12, 2017

@cotsog it's fixed now. Here's my Fastfile for posterity

https://gist.github.com/codeOfRobin/3d01d2ee7feabc35b3a65bd6b319f84c

@cotsog

This comment has been minimized.

Show comment
Hide comment
@cotsog

cotsog Jan 16, 2017

This is now documented in our documentation here: https://docs.travis-ci.com/user/common-build-problems/#Mac%3A-macOS-Sierra-(10.12)-Code-Signing-Errors.

We are now considering this issue closed. Please reach out at support [at] travis-ci [dot] com if you are still having issues.

Thank you for your patience!

cotsog commented Jan 16, 2017

This is now documented in our documentation here: https://docs.travis-ci.com/user/common-build-problems/#Mac%3A-macOS-Sierra-(10.12)-Code-Signing-Errors.

We are now considering this issue closed. Please reach out at support [at] travis-ci [dot] com if you are still having issues.

Thank you for your patience!

framabot pushed a commit to ideascube/pibox-installer that referenced this issue Dec 21, 2017

Fix codesign issue on travis macos
https://stackoverflow.com/questions/40994404/xcodebuild-stuck-at-codesign-step-when-being-run-in-travis-ci#41013151

```
I solved same problem by following steps that is described here.

travis-ci/travis-ci#6791 (comment)

a) change argument for all your security imports to keychain from -T to -A

security import ./scripts/certs/dist.cer -k ~/Library/Keychains/ios-build.keychain -A

b) after all imports execute command set-key-partition-list

security set-key-partition-list -S apple-tool:,apple: -s -k <keychainPass> <keychainName>
```

framabot pushed a commit to ideascube/pibox-installer that referenced this issue Dec 21, 2017

Fix codesign issue on travis macos
https://stackoverflow.com/questions/40994404/xcodebuild-stuck-at-codesign-step-when-being-run-in-travis-ci#41013151

```
I solved same problem by following steps that is described here.

travis-ci/travis-ci#6791 (comment)

a) change argument for all your security imports to keychain from -T to -A

security import ./scripts/certs/dist.cer -k ~/Library/Keychains/ios-build.keychain -A

b) after all imports execute command set-key-partition-list

security set-key-partition-list -S apple-tool:,apple: -s -k <keychainPass> <keychainName>
```

framabot pushed a commit to ideascube/pibox-installer that referenced this issue Dec 21, 2017

Fix codesign issue on travis macos
https://stackoverflow.com/questions/40994404/xcodebuild-stuck-at-codesign-step-when-being-run-in-travis-ci#41013151

```
I solved same problem by following steps that is described here.

travis-ci/travis-ci#6791 (comment)

a) change argument for all your security imports to keychain from -T to -A

security import ./scripts/certs/dist.cer -k ~/Library/Keychains/ios-build.keychain -A

b) after all imports execute command set-key-partition-list

security set-key-partition-list -S apple-tool:,apple: -s -k <keychainPass> <keychainName>
```
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment