Fabric Plugin: Archive Packaging Error: -6 Error re-signing the application for distribution
When I try to upload a new build using the Fabric Plugin I get the following error:
Archive Packaging Error: -6 Error re-signing the application for distribution.
/usr/bin/codesign --sign 937558639C8878BB6E161112505FA2965804A6AE --all-architectures --force --entitlements /var/folders/xf/l7r1f0m54mjbwd9c3myd88zw0000gn/T/com.crashlytics.ipas/A6C80578-CC0E-443D-B81C-C10E972E88F8/Payload/entitlements.xml /var/folders/xf/l7r1f0m54mjbwd9c3myd88zw0000gn/T/com.crashlytics.ipas/A6C80578-CC0E-443D-B81C-C10E972E88F8/Payload/ShowGo.app 937558639C8878BB6E161112505FA2965804A6AE: no identity found
It used to work until the last version of the app. And then for some reason it just stopped working. Here's what I've tried:
- Clean / Rebuild / Archive (many times)
- Uninstall / reinstall Fabric plugin
- Re-download provisioning profiles
- Change from automatic to manual signing
- Searching for missing code signing identity (> security find-identity -p codesigning)
What's killing me is I can't figure out for the life of me where Fabric is pulling that codesign identity value (937558639C8878BB6E161112505FA2965804A6AE) from. It's not in the project as I've grepped for it. Could it be cached somewhere else?
I just had this issue due to removing all my certificates in my Keychain due to signing issues with Xcode.
To solve this, I went into Xcode -> Preferences -> and looked through the accounts added (I have to for this Mac) and made sure that I had the right certificates (checked which ones were needed by them being greyed out).
Using the last line (in this case for the question, it will look different):
937558639C8878BB6E161112505FA2965804A6AE: no identity found
I was able to figure out which certificate was needed via hovering the mouse over the greyed out certificates (I wish it wasn't so hidden!), anyways that solved it for me, hopefully it can help others who have this issue.
So just to iterate, I went onto the apple developer account website -> "Certificates, Identifiers & Profiles" and proceeded to download the certificate that way, despite having auto signing enabled I still had to do this.
Technical Q&A QA1798: Checking Distribution Entitlements, Note: If the live version of your App Store app is affected by missing entitlements, you can not simply re-sign the existing app archive. Once your
I've had the same issue.
It's because your developer account is prolongated and Provision Profiles are invalid.
You need to go to the developer.apple.com and update your Provision Profiles. Then download them, delete old Provision Profiles from Xcode, and tap to the new Profiles for add it to the Xcode! It helped me!
Technical Note TN2431: App Testing Guide, Release is the build configuration used when archiving an app in Xcode, by default. Since archives are the recommended way to distribute all
I had the same issue working with Xcode 9.3 with a developer account included in an educational organization.
I solved it by deselecting the Automatic manage signing option in the Signing panel and by manually downloading the provisioning profile.
To dowload the profile, you have to select the option Download Profile... in the Provisioning Profile menu. Xcode obtains the provisioning profiles from the Member Center, let you select the one and informs you of possible problems.
In my case, my certificate was not present in the provisioning profile and had to recreate it with Xcode and rebuild the provisioning profile in the Member Center.
How to code sign & publish iOS apps, The developer needs to create a Certificate signing request (CSR) from their However, distribution certificates are used to release apps to the App Store resources, frameworks, tools, scripts, libraries, plugins, Info.plist files, assets You can archive an iOS app by going to Xcode > Product > Archive.
I did not find a way to fix fabric plugin. But I found a way to not use it. There is cool tool, called fastlane. Integration tutorial you will found inside fabric plugin (check attached image). And it really works!
Customize your Firebase Crashlytics crash reports, Sign in · Documentation · Guides More. Overview Reference Samples Libraries Distribute Android apps The Fabric SDK is now deprecated and will continue reporting your app's After you reach this threshold, additional values are not saved. Because Crashlytics only sends the logged error report on the next app
Archive Packaging Error: -6 Error re-signing the application for distribution
I finally manage to upload a debug archive into Fabric (plugin) via XCode (not fastlane) by manually set an 'iPhone Distribution' certificate in 'xcode/build settings/code signing identity/debug' as well as an adhoc provisioning profile in 'xcode/build settings/Provisioning profile/debug' instead of the 'iPhone developper certificate' and 'Debug provisionning profile' ones (both on app, widget and rich push extensions)
Distribute iOS apps to testers using fastlane, Note: When distributing iOS applications, including enterprise signed apps, Note: If you're using fastlane in a CI environment, you can also
Continuous integration and deployment for your enterprise hybrid , I automated build, sign/resign and distribution operations that we have… No matter what platform you use for building your mobile app, ionic, cordova, issues, dealing with iOS code signing issues, manual archiving, manual deployment, manual re-packaging, code re-signing, and so on and so forth.
Try Fabric for Unity first, setup Crashlytics using SDK for mobile from Twitter called "Fabric" to Fabric, and see “Download Plugins” on left-hand side, the package Tha is “You're almost there… which can still be distributed, I create the archive for distribution next. 15. Then, in the case of this project of mine, the error occurred.
build_ios_app, gym uses the latest APIs to build and sign your application which results in much faster build times. All archives are stored and accessible in the Xcode Organizer lane :beta do scan gym(scheme: "MyApp") crashlytics end # error block is a different packaging method depending on the version of Xcode you're using.