Error exportarchive no signing certificate ios distribution found

New Issue Checklist

• Updated fastlane to the latest version
• I read the Contribution Guidelines
• I read docs.fastlane.tools
• I searched for existing GitHub issues

Issue Description

I’m trying to setup a build pipeline with fastlane where I can build my app and upload it to Crashlytics. My Apple ID isn’t the admin account in the team (I’m a Member). So I try to submit an ad-hoc build, by specifying the following in my FastFile:
gym(scheme: 'MyApp', export_method: 'ad-hoc')

When building, the app is archived just fine but I repeatedly get these errors:

error: exportArchive: No signing certificate «iOS Distribution» found

Error Domain=IDECodesignResolverErrorDomain Code=1 «No signing certificate «iOS Distribution» found» UserInfo={IDEProvisioningError_UserInfoKey_IDEProvisioningErrorPlatform=com.apple.platform.iphoneos, IDEProvisioningError_UserInfoKey_IDEProvisioningErrorAction=5, NSLocalizedRecoverySuggestion=No «iOS Distribution» signing certificate matching team ID «MY TEAM NAME HERE» with a private key was found., IDEProvisioningError_UserInfoKey_IDEProvisioningErrorSpecifier=iOS Distribution, IDEProvisioningError_UserInfoKey_IDEProvisioningErrorTeam=<IDEProvisioningBasicTeam 0x7fa2b8cce270: teamID: MY TEAM NAME ID HERE, teamName: (null)>, NSLocalizedDescription=No signing certificate «iOS Distribution» found}

However, I’ve been able to upload a build to Crashlytics with the same account through their Mac app. So that tells me I can upload builds from my account and it’s just fastlane that’s messing up (and somehow not honouring the ‘ad-hoc’ variable? Just a guess.)

Environment

✅ fastlane environment ✅

Stack

System Locale

fastlane files:

`./fastlane/Fastfile`

  #
  # Learn more here: https://docs.fastlane.tools/getting-started/ios/beta-deployment/
  #             and: https://docs.fastlane.tools/getting-started/android/beta-deployment/
  #
  lane :beta do |values|
    # Fabric generated this lane for deployment to Crashlytics Beta
    # set 'export_method' to 'ad-hoc' if your Crashlytics Beta distribution uses ad-hoc provisioning
    #get_provisioning_profile
    gym(scheme: 'My APP Name', export_method: 'ad-hoc')

    emails = values[:test_email] ? values[:test_email] : ['email@john.com'] # You can list more emails here
    groups = values[:test_email] ? nil : nil # You can define groups on the web and reference them here

    crashlytics(api_token: 'My Token',
             build_secret: 'My Secret',
                   emails: emails,
                   groups: groups,
                    notes: 'Distributed with fastlane', # Check out the changelog_from_git_commits action
            notifications: true) # Should this distribution notify your testers via email?

    # for all available options run `fastlane action crashlytics`

    # You can notify your team in chat that a beta build has been uploaded
    # slack(
    #   slack_url: "https://hooks.slack.com/services/YOUR/TEAM/INFO"
    #   channel: "beta-releases",
    #   message: "Successfully uploaded a beta release - see it at https://fabric.io/_/beta"
    # )
  end

No Appfile found

fastlane gems

Loaded fastlane plugins:

No plugins Loaded

Loaded gems

generated on: 2017-12-06

Any help is appreciated.

Tags:

Ios

Provisioning Profile

Ipa

Ios Provisioning

Mobileprovision

Nov
22
2016

With Unity Cloud Build service, you can create iOS apps, without ever needing Macintosh+XCode!

First steps

– Register as an Apple Developer : https://developer.apple.com/programs/enroll/
– Join Unity Cloud Build (if you haven’t already) : https://unity3d.com/services/cloud-build
– Follow cloud build instructions there, its quite simple to setup iOS project
(but you’ll need to have the project at source control somewhere, for example github.com, bitbucket.com)

Creating .CSR file in Windows (Certificate Signing Request)

– Download openssl binary : https://indy.fulgan.com/SSL/ (i used this version )
– Unzip it
– Open Command Prompt on that folder  *Note: Must run command prompt as an Administrator!
– Enter following command> openssl genrsa -out mykey.key 2048
– Download missing openssl.cfg file from this page https://docs.oracle.com/cd/E19509-01/820-3503/ggeyz/index.html and place it to the same folder with openssl (with filename openssl.cnf)
– Enter following command> set OPENSSL_CONF=c:YourOpensslFolderopenssl.cnf
– Enter following command> openssl req -new -key mykey.key -out CertificateSigningRequest.certSigningRequest  -subj “/emailAddress=yourAddress@example.com, CN=YourName, C=US”
– Now you can upload the generated “CertificateSigningRequest.certSigningRequest” file into Apple Developer site (when creating the Production Certificate in next step)

Setting Up Apple Developer Licenses

– Login into Apple Developer Account
– Create App ID (make it wildcard, so you can use it for many apps) https://developer.apple.com/account/resources/identifiers/list
– Go to “Certificates, Identifiers & Profiles” https://developer.apple.com/account/resources/certificates/list
– Create Distribution certificate (“iOS Distribution (App Store and Ad Hoc)”, cloud build says so)
– Upload signing certificate (its the file you created in earlier steps here)
– Download it (ios_distribution.cer)

Creating .p12 file in Windows

– Download your “ios_distribution.cer” from previous step (and copy it into your openssl folder)
– Open command prompt (NOTE run as administrator)
– Enter following command> openssl x509 -in ios_distribution.cer -inform DER -out developer_identity.pem -outform PEM
– (Uses the mykey.key we created in CRS creation)
– Enter following command> openssl pkcs12 -export -inkey mykey.key -in developer_identity.pem -out iphone_dev.p12
– enter password (write it down, as you will need it later) *Note: if you paste the password in from notepad, it might not work(?)

Creating .mobileProvision file

– Register a New Provisioning Profile at https://developer.apple.com/account/resources/profiles/list
– Select Adhoc, continue
– Select AppID (select your wildcard id from there), continue
– Select certificate from list (should be todays date), continue
– Select devices (all, you need to have them added first in devices place), continue
– Set “Provisioning Profile Name”
– Click Generate
– Click Download “yourfile.mobileprovision”

Building .ipa with Unity cloud build

– Go to unity cloud build: https://unity3d.com/services/cloud-build
– Create new IOS Project (just follow the instructions on the site, its quite simple)
– And when it asks for the Mobile Prov File and .p12 files, you now have them!
– Then hit Build and download your .ipa file

Copying .ipa to iOS Device

– Note this is not tested on 2022.. since there is no itunes access to pad anymore either? (but you can use those generated cert files in Unity Cloud build)
– Install iTunes
– Connect ios device to your pc
– Click […] and select Apps (shows all available apps on this machine, not from the ipad)
– Remove your old app from the list (if its there), right click, delete
– Then drag and drop the cloud build .ipa file here (cannot drag and drop it directly to the ipad)
– Then click [] Ipad icon to view your ipad
– Click Apps (in left panel)
– Scroll down to see your .ipa app listed there
– Click Install (or Update) button *it changes to Will Install or Will Update
– Click Apply button at the bottom
– Done! You can now run the app on ipad
*Note: First you need to authorize and sync the ipad to this machine

—

References:
https://unity3d.com/learn/tutorials/topics/cloud-build/your-first-cloud-build-project
http://help.adobe.com/en_US/as3/iphone/WS144092a96ffef7cc-371badff126abc17b1f-7fff.html
http://help.adobe.com/en_US/as3/iphone/WS144092a96ffef7cc-371badff126abc17b1f-8000.html
https://www.tbs-certificates.co.uk/FAQ/en/openssl-windows.html
http://docs.telerik.com/platform/appbuilder/cordova/code-signing-your-app/configuring-code-signing-for-ios-apps/create-distribution-certificate

Errors:
“Failed to update credentials! The provisioning profile and .p12 file are not compatible (certificates did not match)!”

Generate your keys again, probably used wrong file or wrong password in some step..