Build fails with IDEDistributionErrorDomain Code=1 #100

Closed
drpancake opened this Issue Sep 23, 2015 · 33 comments

Comments

Projects
None yet
@drpancake

Hello,

Google isn't turning up anything for this one and I can't seem to find any definitions for codes in IDEDistributionErrorDomain. I'm seeing the following error when I run gym:

[09:16:52]: Successfully stored the archive. You can find it in the Xcode Organizer.
[09:16:52]: /usr/bin/xcrun xcodebuild -exportArchive -exportOptionsPlist '/tmp/gym_config_1442974612.plist' -archivePath '/Users/james/Library/Developer/Xcode/Archives/2015-09-23/SiphonBase 2015-09-23 09.16.00.xcarchive' -exportPath '/tmp/1442974612'
2015-09-23 09:16:53.275 xcodebuild[7281:1574120] [MT] IDEDistribution: -[IDEDistributionLogging _createLoggingBundleAtPath:]: Created bundle at path '/var/folders/x5/_ydv1yb97r17pzpsk4h7vrzm0000gn/T/SiphonBase_2015-09-23_09-16-53.272.xcdistributionlogs'.
2015-09-23 09:16:53.532 xcodebuild[7281:1574120] [MT] IDEDistribution: Step failed: <IDEDistributionSigningAssetsStep: 0x7ffdcd5246f0>: Error Domain=IDEDistributionErrorDomain Code=1 "The operation couldn’t be completed. (IDEDistributionErrorDomain error 1.)"
error: exportArchive: The operation couldn’t be completed. (IDEDistributionErrorDomain error 1.)

Error Domain=IDEDistributionErrorDomain Code=1 "The operation couldn’t be completed. (IDEDistributionErrorDomain error 1.)"

** EXPORT FAILED **
[09:16:53]: Exit status: 70
/Library/Ruby/Gems/2.0.0/gems/gym-0.7.3/lib/gym/error_handler.rb:88:in `handle_package_error': Error packaging up the application (RuntimeError)
    from /Library/Ruby/Gems/2.0.0/gems/gym-0.7.3/lib/gym/runner.rb:102:in `block in package_app'
    from /Library/Ruby/Gems/2.0.0/gems/fastlane_core-0.17.1/lib/fastlane_core/command_executor.rb:51:in `call'
    from /Library/Ruby/Gems/2.0.0/gems/fastlane_core-0.17.1/lib/fastlane_core/command_executor.rb:51:in `execute'
    from /Library/Ruby/Gems/2.0.0/gems/gym-0.7.3/lib/gym/runner.rb:98:in `package_app'
    from /Library/Ruby/Gems/2.0.0/gems/gym-0.7.3/lib/gym/runner.rb:16:in `run'
    from /Library/Ruby/Gems/2.0.0/gems/gym-0.7.3/lib/gym/manager.rb:8:in `work'
    from /Library/Ruby/Gems/2.0.0/gems/gym-0.7.3/lib/gym/commands_generator.rb:41:in `block (2 levels) in run'
    from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/command.rb:178:in `call'
    from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/command.rb:178:in `call'
    from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/command.rb:153:in `run'
    from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/runner.rb:428:in `run_active_command'
    from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/runner.rb:68:in `run!'
    from /Library/Ruby/Gems/2.0.0/gems/commander-4.3.5/lib/commander/delegates.rb:15:in `run!'
    from /Library/Ruby/Gems/2.0.0/gems/gym-0.7.3/lib/gym/commands_generator.rb:58:in `run'
    from /Library/Ruby/Gems/2.0.0/gems/gym-0.7.3/lib/gym/commands_generator.rb:14:in `start'
    from /Library/Ruby/Gems/2.0.0/gems/gym-0.7.3/bin/gym:6:in `<top (required)>'
    from /usr/bin/gym:23:in `load'
    from /usr/bin/gym:23:in `<main>'
@KrauseFx

This comment has been minimized.

Show comment
Hide comment
@KrauseFx

KrauseFx Sep 23, 2015

Contributor

You could try to use the use_legacy_build_api option as it seems like the new way of code signing is quite buggy.

Contributor

KrauseFx commented Sep 23, 2015

You could try to use the use_legacy_build_api option as it seems like the new way of code signing is quite buggy.

@drpancake

This comment has been minimized.

Show comment
Hide comment
@drpancake

drpancake Sep 23, 2015

Works perfectly, thanks.

Works perfectly, thanks.

@KrauseFx

This comment has been minimized.

Show comment
Hide comment

@KrauseFx KrauseFx closed this Sep 23, 2015

andreaskumlehn added a commit to FAU-Inf2/fablab-ios that referenced this issue Oct 9, 2015

@rcedwards

This comment has been minimized.

Show comment
Hide comment
@rcedwards

rcedwards Jan 11, 2016

I'm still seeing this issue with 1.3.0. Was there a reason why this issue was closed?

I'm still seeing this issue with 1.3.0. Was there a reason why this issue was closed?

@rcedwards

This comment has been minimized.

Show comment
Hide comment
@rcedwards

rcedwards Jan 12, 2016

Also present in 1.4.0

Also present in 1.4.0

@ANTARESXXI

This comment has been minimized.

Show comment
Hide comment
@ANTARESXXI

ANTARESXXI Jan 13, 2016

Getting this error in 1.4.0

Getting this error in 1.4.0

@ANTARESXXI

This comment has been minimized.

Show comment
Hide comment
@ANTARESXXI

ANTARESXXI Jan 26, 2016

Is there any fix for this?

Is there any fix for this?

@vpolouchkine

This comment has been minimized.

Show comment
Hide comment
@vpolouchkine

vpolouchkine Jan 30, 2016

Contributor

Have you tried use_legacy_build_api?

Contributor

vpolouchkine commented Jan 30, 2016

Have you tried use_legacy_build_api?

@ANTARESXXI

This comment has been minimized.

Show comment
Hide comment
@ANTARESXXI

ANTARESXXI Feb 2, 2016

@vpolouchkine use_legacy_build_api doesn't create "WatchKitSupport" (and other folders) for me

@vpolouchkine use_legacy_build_api doesn't create "WatchKitSupport" (and other folders) for me

@ohayon

This comment has been minimized.

Show comment
Hide comment
@ohayon

ohayon Feb 10, 2016

Contributor

hey all, I'm definitely going to do some more digging here, but is it safe to assume you have seen this answer on SO? http://stackoverflow.com/a/32841301 not sure if that is helpful or relevant, but let me know if you have already checked that out and in the mean time i will take a deeper look.. thanks! 🐙

Contributor

ohayon commented Feb 10, 2016

hey all, I'm definitely going to do some more digging here, but is it safe to assume you have seen this answer on SO? http://stackoverflow.com/a/32841301 not sure if that is helpful or relevant, but let me know if you have already checked that out and in the mean time i will take a deeper look.. thanks! 🐙

@kommen

This comment has been minimized.

Show comment
Hide comment
@kommen

kommen Feb 10, 2016

I just ran into the same error. For me the solution was to ensure all signing assets are present. (I only had development assets installed with match, was missing the appstore assets).

kommen commented Feb 10, 2016

I just ran into the same error. For me the solution was to ensure all signing assets are present. (I only had development assets installed with match, was missing the appstore assets).

@ohayon ohayon added bug and removed awaiting response labels Feb 10, 2016

@ohayon

This comment has been minimized.

Show comment
Hide comment
@ohayon

ohayon Feb 10, 2016

Contributor

@drpancake would you mind giving a shot what worked for @kommen ? thanks!!

Contributor

ohayon commented Feb 10, 2016

@drpancake would you mind giving a shot what worked for @kommen ? thanks!!

@ohayon ohayon closed this Feb 10, 2016

@owurman

This comment has been minimized.

Show comment
Hide comment
@owurman

owurman Feb 14, 2016

Not sure if this gives any hints, but I just had this fail after a successful run of building/signing/uploading, then having to self-reject (remove from review) because I found a bug, then trying again. So it succeeded the first time, then failed the second time.

Edit to add: just noticed you closed this. Is it fixed in an upcoming release? I'm using the latest fastlane 1.59.0, deliver and gym

Edit 2: Trying to fall back on use_legacy_build_api gives me this error:

[Transporter Error Output]: ERROR ITMS-90161: "Invalid Provisioning Profile. The provisioning profile included in the bundle ### is invalid. [Missing code-signing certificate]. A Distribution Provisioning profile should be used when submitting apps to the App Store. For more information, visit the iOS Developer Portal."

I'm not sure why it's giving me this now when it wasn't the first time. I'll look into it.

owurman commented Feb 14, 2016

Not sure if this gives any hints, but I just had this fail after a successful run of building/signing/uploading, then having to self-reject (remove from review) because I found a bug, then trying again. So it succeeded the first time, then failed the second time.

Edit to add: just noticed you closed this. Is it fixed in an upcoming release? I'm using the latest fastlane 1.59.0, deliver and gym

Edit 2: Trying to fall back on use_legacy_build_api gives me this error:

[Transporter Error Output]: ERROR ITMS-90161: "Invalid Provisioning Profile. The provisioning profile included in the bundle ### is invalid. [Missing code-signing certificate]. A Distribution Provisioning profile should be used when submitting apps to the App Store. For more information, visit the iOS Developer Portal."

I'm not sure why it's giving me this now when it wasn't the first time. I'll look into it.

@hjanuschka

This comment has been minimized.

Show comment
Hide comment
@hjanuschka

hjanuschka Feb 14, 2016

in my case this was triggerd by an outdated WWDR certificate (expired on 14/02/16), wich invalidated all my distribution certificates.

download the wwdr https://www.apple.com/certificateauthority/ (here: https://developer.apple.com/certificationauthority/AppleWWDRCA.cer)

double-click/install it and the see if your distribution certs are valid again!

@KrauseFx - maybe checking the certs against the wwdr in match would be a cool thing?

in my case this was triggerd by an outdated WWDR certificate (expired on 14/02/16), wich invalidated all my distribution certificates.

download the wwdr https://www.apple.com/certificateauthority/ (here: https://developer.apple.com/certificationauthority/AppleWWDRCA.cer)

double-click/install it and the see if your distribution certs are valid again!

@KrauseFx - maybe checking the certs against the wwdr in match would be a cool thing?

@owurman

This comment has been minimized.

Show comment
Hide comment
@owurman

owurman Feb 15, 2016

Yes, this fixed it for me, too. For anyone else experiencing the issue, make sure to also delete the expired certificate following the instructions here:
https://www.reddit.com/r/iOSProgramming/comments/45siza/this_certificate_has_an_invalid_issuer/

  1. Open up Keychain Access.
  2. Show expired certificates by going to View > Show Expired Certificates.
  3. Navigate to the System keychain and delete the expired WWDR Certificate.
  4. Download the new WWDR Certificate here and import it into your keychain.

I got confused on step 3--you have to select the System keychain at the top left, it's not enough to delete it from the certificates in the login keychain.

owurman commented Feb 15, 2016

Yes, this fixed it for me, too. For anyone else experiencing the issue, make sure to also delete the expired certificate following the instructions here:
https://www.reddit.com/r/iOSProgramming/comments/45siza/this_certificate_has_an_invalid_issuer/

  1. Open up Keychain Access.
  2. Show expired certificates by going to View > Show Expired Certificates.
  3. Navigate to the System keychain and delete the expired WWDR Certificate.
  4. Download the new WWDR Certificate here and import it into your keychain.

I got confused on step 3--you have to select the System keychain at the top left, it's not enough to delete it from the certificates in the login keychain.

@rad182

This comment has been minimized.

Show comment
Hide comment
@rad182

rad182 Feb 15, 2016

installing the wwdr fixed for me. thanks @hjanuschka

rad182 commented Feb 15, 2016

installing the wwdr fixed for me. thanks @hjanuschka

@philipengberg

This comment has been minimized.

Show comment
Hide comment
@philipengberg

philipengberg Feb 15, 2016

WWDR worked for me as well

WWDR worked for me as well

@izqui

This comment has been minimized.

Show comment
Hide comment
@izqui

izqui Feb 15, 2016

Is it possible to do this from the command line? My travis ci build is failing and I don't know how to update the certificate.

izqui commented Feb 15, 2016

Is it possible to do this from the command line? My travis ci build is failing and I don't know how to update the certificate.

@n8stowell82

This comment has been minimized.

Show comment
Hide comment
@n8stowell82

n8stowell82 Feb 15, 2016

same for me but with circle ci

same for me but with circle ci

@hjanuschka

This comment has been minimized.

Show comment
Hide comment
@hjanuschka

hjanuschka Feb 15, 2016

well, untested, and not 100% from me (dicussed on fastlane slack thx to @xfreebird )

this should do it - or maybe one of it (not sure wich keychain on wich CI has to be fixed):

  • system keychain
sudo security delete-certificate -c "Apple Worldwide Developer Relations Certification Authority" /Library/Keychains/System.keychain

curl -O -L http://developer.apple.com/certificationauthority/AppleWWDRCA.cer
sudo security import AppleWWDRCA.cer  -k /Library/Keychains/System.keychain -A
  • user keychain:
security delete-certificate -c "Apple Worldwide Developer Relations Certification Authority"  ~/Library/Keychains/login.keychain

curl -O -L http://developer.apple.com/certificationauthority/AppleWWDRCA.cer
security import AppleWWDRCA.cer  -k ~/Library/Keychains/login.keychain -A

to show if the WWDRC is expired do a:

security find-certificate -p -c "Apple Worldwide Developer Relations Certification Authority" |openssl x509 -checkend 86400 -noout

exit code 0 if it does not exipre within 1day, exit code 1 if it expires within 1 day

well, untested, and not 100% from me (dicussed on fastlane slack thx to @xfreebird )

this should do it - or maybe one of it (not sure wich keychain on wich CI has to be fixed):

  • system keychain
sudo security delete-certificate -c "Apple Worldwide Developer Relations Certification Authority" /Library/Keychains/System.keychain

curl -O -L http://developer.apple.com/certificationauthority/AppleWWDRCA.cer
sudo security import AppleWWDRCA.cer  -k /Library/Keychains/System.keychain -A
  • user keychain:
security delete-certificate -c "Apple Worldwide Developer Relations Certification Authority"  ~/Library/Keychains/login.keychain

curl -O -L http://developer.apple.com/certificationauthority/AppleWWDRCA.cer
security import AppleWWDRCA.cer  -k ~/Library/Keychains/login.keychain -A

to show if the WWDRC is expired do a:

security find-certificate -p -c "Apple Worldwide Developer Relations Certification Authority" |openssl x509 -checkend 86400 -noout

exit code 0 if it does not exipre within 1day, exit code 1 if it expires within 1 day

@n8stowell82

This comment has been minimized.

Show comment
Hide comment
@n8stowell82

n8stowell82 Feb 15, 2016

Awesome thanks for this! So it looks like the cert will expire for me, do I need to run both system and user on the CI server? or should I just run system?

Awesome thanks for this! So it looks like the cert will expire for me, do I need to run both system and user on the CI server? or should I just run system?

@hjanuschka

This comment has been minimized.

Show comment
Hide comment
@hjanuschka

hjanuschka Feb 15, 2016

i am not 100% sure, as it is sandboxed on travis for e.g.: just give it a try wich one works for you, maybe you require both.

i am not 100% sure, as it is sandboxed on travis for e.g.: just give it a try wich one works for you, maybe you require both.

@izqui

This comment has been minimized.

Show comment
Hide comment
@izqui

izqui Feb 15, 2016

I ran this script on before-install:

#!/bin/bash

security delete-certificate -c "Apple Worldwide Developer Relations Certification Authority" /Library/Keychains/System.keychain
security delete-certificate -c "Apple Worldwide Developer Relations Certification Authority" /Library/Keychains/login.keychain
curl -O -L http://developer.apple.com/certificationauthority/AppleWWDRCA.cer
security import AppleWWDRCA.cer  -k ~/Library/Keychains/login.keychain -A

and the Travis output was like this:

security: "Apple Worldwide Developer Relations Certification Authority" is ambiguous, matches more than one certificate
Unable to delete certificate matching "Apple Worldwide Developer Relations Certification Authority"Unable to delete certificate matching "Apple Worldwide Developer Relations Certification Authority"  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   178  100   178    0     0    270      0 --:--:-- --:--:-- --:--:--   270
100  1062  100  1062    0     0    439      0  0:00:02  0:00:02 --:--:--  2386
1 certificate imported.

Regardless of that, gym did the build just fine 👍

izqui commented Feb 15, 2016

I ran this script on before-install:

#!/bin/bash

security delete-certificate -c "Apple Worldwide Developer Relations Certification Authority" /Library/Keychains/System.keychain
security delete-certificate -c "Apple Worldwide Developer Relations Certification Authority" /Library/Keychains/login.keychain
curl -O -L http://developer.apple.com/certificationauthority/AppleWWDRCA.cer
security import AppleWWDRCA.cer  -k ~/Library/Keychains/login.keychain -A

and the Travis output was like this:

security: "Apple Worldwide Developer Relations Certification Authority" is ambiguous, matches more than one certificate
Unable to delete certificate matching "Apple Worldwide Developer Relations Certification Authority"Unable to delete certificate matching "Apple Worldwide Developer Relations Certification Authority"  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   178  100   178    0     0    270      0 --:--:-- --:--:-- --:--:--   270
100  1062  100  1062    0     0    439      0  0:00:02  0:00:02 --:--:--  2386
1 certificate imported.

Regardless of that, gym did the build just fine 👍

@pedro380085

This comment has been minimized.

Show comment
Hide comment
@pedro380085

pedro380085 Feb 16, 2016

it also worked for me!

it also worked for me!

@n8stowell82

This comment has been minimized.

Show comment
Hide comment
@n8stowell82

n8stowell82 Feb 16, 2016

yes using izqui's script worked great for me. Thanks!

yes using izqui's script worked great for me. Thanks!

@lluisgerard

This comment has been minimized.

Show comment
Hide comment
@lluisgerard

lluisgerard Feb 16, 2016

@izqui security delete-certificate didn't work for me, I had to manually delete the certificates on the Keychain app, then the import worked. Thanks 👍

@izqui security delete-certificate didn't work for me, I had to manually delete the certificates on the Keychain app, then the import worked. Thanks 👍

@pesterhazy

This comment has been minimized.

Show comment
Hide comment
@pesterhazy

pesterhazy Feb 16, 2016

I have no idea what triggered it, but something changed and broke the builds for our team. @izqui's fix worked for me.

Any chance you could include this step (or at least a check that the certs are up to date, with a link to the github issue) in gym?

I have no idea what triggered it, but something changed and broke the builds for our team. @izqui's fix worked for me.

Any chance you could include this step (or at least a check that the certs are up to date, with a link to the github issue) in gym?

@pesterhazy

This comment has been minimized.

Show comment
Hide comment
@pesterhazy

pesterhazy Feb 16, 2016

Updated script based on @izqui: https://gist.github.com/pesterhazy/0c176b6ee28d8fa2a944 (adds sudo in the right places)

Updated script based on @izqui: https://gist.github.com/pesterhazy/0c176b6ee28d8fa2a944 (adds sudo in the right places)

@freynolds

This comment has been minimized.

Show comment
Hide comment
@freynolds

freynolds Feb 16, 2016

Hey @KrauseFx that worked 10points!
Thank you for your help and excelent tools!

Hey @KrauseFx that worked 10points!
Thank you for your help and excelent tools!

@Sega-Zero Sega-Zero referenced this issue in travis-ci/travis-ci Feb 16, 2016

Closed

Get rid of expired apple certificate #5633

@dugalp

This comment has been minimized.

Show comment
Hide comment
@dugalp

dugalp Feb 17, 2016

Thank you all, the WWDR cert was expired on my system as well. Here is the error I received:
build 17-Feb-2016 10:49:35 [10:49:35]: �[32mSuccessfully stored the archive. You can find it in the Xcode Organizer.�[0m
build 17-Feb-2016 10:49:35 [10:49:35]: �[4m�[36m$ /usr/bin/xcrun /Library/Ruby/Gems/2.0.0/gems/gym-1.4.0/lib/assets/wrap_xcodebuild/xcbuild-safe.sh -exportArchive -exportOptionsPlist '/var/folders/l2/jdpt2gfd3g1g6p965jn22d140000gk/T/gym20160217-64963-yj72dm_config.plist' -archivePath '/Users/myusername/Library/Developer/Xcode/Archives/2016-02-17/MyApp 2016-02-17 10.47.32.xcarchive' -exportPath '/var/folders/l2/jdpt2gfd3g1g6p965jn22d140000gk/T/gym20160217-64963-qgap78.gym_output' �[0m�[0m
build 17-Feb-2016 10:49:37 + xcodebuild -exportArchive -exportOptionsPlist /var/folders/l2/jdpt2gfd3g1g6p965jn22d140000gk/T/gym20160217-64963-yj72dm_config.plist -archivePath '/Users/myusername/Library/Developer/Xcode/Archives/2016-02-17/MyApp 2016-02-17 10.47.32.xcarchive' -exportPath /Users/folders/l2/jdpt2gfd3g1g6p965jn22d140000gk/T/gym20160217-64963-qgap78.gym_output
build 17-Feb-2016 10:49:37 2016-02-17 10:49:36.164 xcodebuild[70003:11042250] [MT] IDEDistribution: -[IDEDistributionLogging _createLoggingBundleAtPath:]: Created bundle at path '/var/folders/l2/jdpt2gfd3g1g6p965jn22d140000gk/T/MyApp_2016-02-17_10-49-36.164.xcdistributionlogs'.
build 17-Feb-2016 10:49:37 2016-02-17 10:49:37.751 xcodebuild[70003:11042250] [MT] IDEDistribution: Step failed: <IDEDistributionSigningAssetsStep: 0x7fb3c462f500>: Error Domain=IDEDistributionErrorDomain Code=1 "The operation couldn’t be completed. (IDEDistributionErrorDomain error 1.)"
build 17-Feb-2016 10:49:37 error: exportArchive: The operation couldn’t be completed. (IDEDistributionErrorDomain error 1.)
build 17-Feb-2016 10:49:37
build 17-Feb-2016 10:49:37 Error Domain=IDEDistributionErrorDomain Code=1 "The operation couldn’t be completed. (IDEDistributionErrorDomain error 1.)"
build 17-Feb-2016 10:49:37
build 17-Feb-2016 10:49:37 ** EXPORT FAILED **
build 17-Feb-2016 10:49:37 [10:49:37]: �[31mExit status: 70�[0m
error 17-Feb-2016 10:49:37 �[31m
error 17-Feb-2016 10:49:37 [!] Error packaging up the application�[0m

Adding the new cert on the system solved it!

dugalp commented Feb 17, 2016

Thank you all, the WWDR cert was expired on my system as well. Here is the error I received:
build 17-Feb-2016 10:49:35 [10:49:35]: �[32mSuccessfully stored the archive. You can find it in the Xcode Organizer.�[0m
build 17-Feb-2016 10:49:35 [10:49:35]: �[4m�[36m$ /usr/bin/xcrun /Library/Ruby/Gems/2.0.0/gems/gym-1.4.0/lib/assets/wrap_xcodebuild/xcbuild-safe.sh -exportArchive -exportOptionsPlist '/var/folders/l2/jdpt2gfd3g1g6p965jn22d140000gk/T/gym20160217-64963-yj72dm_config.plist' -archivePath '/Users/myusername/Library/Developer/Xcode/Archives/2016-02-17/MyApp 2016-02-17 10.47.32.xcarchive' -exportPath '/var/folders/l2/jdpt2gfd3g1g6p965jn22d140000gk/T/gym20160217-64963-qgap78.gym_output' �[0m�[0m
build 17-Feb-2016 10:49:37 + xcodebuild -exportArchive -exportOptionsPlist /var/folders/l2/jdpt2gfd3g1g6p965jn22d140000gk/T/gym20160217-64963-yj72dm_config.plist -archivePath '/Users/myusername/Library/Developer/Xcode/Archives/2016-02-17/MyApp 2016-02-17 10.47.32.xcarchive' -exportPath /Users/folders/l2/jdpt2gfd3g1g6p965jn22d140000gk/T/gym20160217-64963-qgap78.gym_output
build 17-Feb-2016 10:49:37 2016-02-17 10:49:36.164 xcodebuild[70003:11042250] [MT] IDEDistribution: -[IDEDistributionLogging _createLoggingBundleAtPath:]: Created bundle at path '/var/folders/l2/jdpt2gfd3g1g6p965jn22d140000gk/T/MyApp_2016-02-17_10-49-36.164.xcdistributionlogs'.
build 17-Feb-2016 10:49:37 2016-02-17 10:49:37.751 xcodebuild[70003:11042250] [MT] IDEDistribution: Step failed: <IDEDistributionSigningAssetsStep: 0x7fb3c462f500>: Error Domain=IDEDistributionErrorDomain Code=1 "The operation couldn’t be completed. (IDEDistributionErrorDomain error 1.)"
build 17-Feb-2016 10:49:37 error: exportArchive: The operation couldn’t be completed. (IDEDistributionErrorDomain error 1.)
build 17-Feb-2016 10:49:37
build 17-Feb-2016 10:49:37 Error Domain=IDEDistributionErrorDomain Code=1 "The operation couldn’t be completed. (IDEDistributionErrorDomain error 1.)"
build 17-Feb-2016 10:49:37
build 17-Feb-2016 10:49:37 ** EXPORT FAILED **
build 17-Feb-2016 10:49:37 [10:49:37]: �[31mExit status: 70�[0m
error 17-Feb-2016 10:49:37 �[31m
error 17-Feb-2016 10:49:37 [!] Error packaging up the application�[0m

Adding the new cert on the system solved it!

@jaymuthialu

This comment has been minimized.

Show comment
Hide comment
@jaymuthialu

jaymuthialu Feb 17, 2016

We got FastLane errors during build process (gym). Error message: Could not provisional profile. This happened in Travis. Our setup was working fine until then and I was not sure what triggered the issue. I rechecked multiple times all the certs and Provisional profiles and they were setup correctly. After spending quite some time to identify and isolate the issue, I figured it could be because expiration of Apple WWDR certificate. I followed the post given by Apple to fix the issue and this fixed in my local machine. However it did not work in Travis.

I followed @hjanuschka script and it worked like a charm. Here is the script I used to solve our issue:

Use this script in before_install:

  • sudo security delete-certificate -c "Apple Worldwide Developer Relations Certification Authority" /Library/Keychains/System.keychain
  • curl -O -L http://developer.apple.com/certificationauthority/AppleWWDRCA.cer
  • sudo security import AppleWWDRCA.cer -k /Library/Keychains/System.keychain -A
  • sudo security import AppleWWDRCA.cer -k ~/Library/Keychains/login.keychain -A

You can also try removing the certificate in local.KeyChain but it did not work for me as there was no certificate found in local keychain in Travis CI.

We got FastLane errors during build process (gym). Error message: Could not provisional profile. This happened in Travis. Our setup was working fine until then and I was not sure what triggered the issue. I rechecked multiple times all the certs and Provisional profiles and they were setup correctly. After spending quite some time to identify and isolate the issue, I figured it could be because expiration of Apple WWDR certificate. I followed the post given by Apple to fix the issue and this fixed in my local machine. However it did not work in Travis.

I followed @hjanuschka script and it worked like a charm. Here is the script I used to solve our issue:

Use this script in before_install:

  • sudo security delete-certificate -c "Apple Worldwide Developer Relations Certification Authority" /Library/Keychains/System.keychain
  • curl -O -L http://developer.apple.com/certificationauthority/AppleWWDRCA.cer
  • sudo security import AppleWWDRCA.cer -k /Library/Keychains/System.keychain -A
  • sudo security import AppleWWDRCA.cer -k ~/Library/Keychains/login.keychain -A

You can also try removing the certificate in local.KeyChain but it did not work for me as there was no certificate found in local keychain in Travis CI.

@danipralea

This comment has been minimized.

Show comment
Hide comment
@danipralea

danipralea Feb 24, 2016

Hello and many thanks for this tool and all the other ones!
I am trying to integrate fastlane in my application, and it currently fails at gym

I moved to separate gym commands and I have this error:
INFO [2016-02-24 13:05:38.09]: ▸ 2016-02-24 13:05:38.095 xcodebuild[30404:300376] [MT] IDEDistribution: Step failed: <IDEDistributionSigningAssetsStep: 0x7fa7659d6bc0>: Error Domain=IDEDistributionErrorDomain Code=1 "(null)" INFO [2016-02-24 13:05:38.09]: ▸ error: exportArchive: The operation couldn’t be completed. (IDEDistributionErrorDomain error 1.) INFO [2016-02-24 13:05:38.09]: ▸ Error Domain=IDEDistributionErrorDomain Code=1 "(null)" INFO [2016-02-24 13:05:38.09]: ▸ ** EXPORT FAILED **
I also tried the previous solutions (including re-generating the Apple WWDR), but those didn't worked for me

But with this the command is successful and the ipa file is generated:
gym --use_legacy_build_api

What is the disadvantage of using this command? Can I add it to my Gymfile? or Fastfile?

Hello and many thanks for this tool and all the other ones!
I am trying to integrate fastlane in my application, and it currently fails at gym

I moved to separate gym commands and I have this error:
INFO [2016-02-24 13:05:38.09]: ▸ 2016-02-24 13:05:38.095 xcodebuild[30404:300376] [MT] IDEDistribution: Step failed: <IDEDistributionSigningAssetsStep: 0x7fa7659d6bc0>: Error Domain=IDEDistributionErrorDomain Code=1 "(null)" INFO [2016-02-24 13:05:38.09]: ▸ error: exportArchive: The operation couldn’t be completed. (IDEDistributionErrorDomain error 1.) INFO [2016-02-24 13:05:38.09]: ▸ Error Domain=IDEDistributionErrorDomain Code=1 "(null)" INFO [2016-02-24 13:05:38.09]: ▸ ** EXPORT FAILED **
I also tried the previous solutions (including re-generating the Apple WWDR), but those didn't worked for me

But with this the command is successful and the ipa file is generated:
gym --use_legacy_build_api

What is the disadvantage of using this command? Can I add it to my Gymfile? or Fastfile?

@fastlanebot

This comment has been minimized.

Show comment
Hide comment
@fastlanebot

fastlanebot Mar 8, 2016

This issue was migrated to fastlane/fastlane#3188. Please post all further comments there.

fastlane is now a mono repo, you can read more about the change in our blog post. All tools are now available in the fastlane main repo 🚀

This issue was migrated to fastlane/fastlane#3188. Please post all further comments there.

fastlane is now a mono repo, you can read more about the change in our blog post. All tools are now available in the fastlane main repo 🚀

@fastlanebot fastlanebot added the migrated label Mar 8, 2016

@fastlane-old fastlane-old locked and limited conversation to collaborators Mar 11, 2016

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.