Integrate Fabric/Crashlytics via CocoaPods

Question

I try to integrate Fabric/Crashlytics via CocoaPods, my Podfile looks like this:

pod 'Fabric/Core', '1.2'
pod 'Fabric/Crashlytics', '1.2'

But when I try to build my app, the build fails and I get a Shell Script Invocation Error that the run script isn't found:

.../Script-F8D74CB61AB5D7A50013D134.sh: line 2: ./Fabric.framework/run: No such file or directory

Is it possible to install Fabric only using CocoaPods?

Why don't you use the Fabric App that automatically installs the SDK and generates your App ID etc? — Daniel Galasko, Mar 16 '15 at 07:11
because I like updating external frameworks via Cocoapods and would love to have everything in one place. — swalkner, Mar 16 '15 at 07:19
Any other pros and cons of pod approach vs. using the app installation? — Bradley Thomas, May 13 '15 at 13:57
I have encountered far too many build errors after updating via the Fabric App. So I have gone back to the good ol' pod. +1 @swalkner — Benjamin, Dec 01 '15 at 11:30

Steven Hepting · Accepted Answer · 2016-01-26T21:56:01.077

167

Fabric now supports installation with CocoaPods: http://docs.fabric.io/ios/fabric/cocoapods.html

If you are just looking for Crashlytics you can use these two pods:

pod 'Fabric'
pod 'Crashlytics'

Along with adding the following build phase script (note: In case the path to your repo contains spaces, you will need the quotes):

"${PODS_ROOT}"/Fabric/run <API Key> <Build Secret>

Run Script Build Phase

If you are looking to use TwitterKit you will need to include:

pod 'TwitterKit'

edited Jan 26 '16 at 21:56

answered Jul 15 '15 at 20:09

Steven Hepting

12,394
8
40
50

9

Folks who get here after the great Crashlytics Cocoapods cataclysm of 2015-07-15 should upvote this answer to push it up the page. THIS should be the accepted answer now. – Mark Edington Jul 15 '15 at 21:02
1

This does not work if you build crashlytics into a local pod and include the local pod in your final target. – dcow Jul 16 '15 at 01:10
@dcow Is there any way currently to use Crashlytics in a pod, rather than in your final target. I'm trying to make this work right now. – AnthonyMDev Jul 17 '15 at 18:26
1

@AnthonyM https://github.com/CocoaPods/Specs/pull/13315 fixed the issue for the Crashlytics pod. The root appears to be a greater bug in CocoaPods, though. – dcow Jul 17 '15 at 18:52
@dcow Thank you. https://github.com/CocoaPods/CocoaPods/issues/2926 It seems that this isn't a bug in CocoaPods, but a limitation of Xcode. Until Crashlytics is released as a dynamic framework, rather than a static library, you won't be able to have a dependency on Crashlytics in a pod spec. – AnthonyMDev Jul 17 '15 at 20:12
Another note, for some reason I couldn't get this to work when installing TwitterKit pod on my own. After uninstalling, Fabric still said I had it "Installed". So I had to comment out all of my TwitterKit code including Imports so it would build, Click the "Installed" button in Fabric, and then it told me to install both the TwitterKit pod AND the TwitterCore pod. I don't understand why it's like this. If you install the TwitterKit pod, shouldn't it auto install the TwitterCore pod? Isn't that the whole point of using Cocoapods? – user3344977 Jul 17 '15 at 22:18
@AnthonyM I'm not sure the issue is exactly the same. The headers aren't even visible to the static library linking against the framework. For example, I can't `#import ` even in the pod that has the direct dependency on Fabric and Crashlytics. – dcow Jul 17 '15 at 23:07
I had a persistent build error with the Run Script phase as advised, until I removed the double quotes from around the command. – Jere Käpyaho Aug 10 '15 at 16:46
6

In case the path to your repo contains spaces, you might want to do `"${PODS_ROOT}"/Fabric/Fabric.framework/run` (note the quotes) – nevyn Sep 22 '15 at 18:10
This comment helped me when I wanted to remove Crashlytics and Fabric from my project. Make sure to remove above run script from your Build Phases. – Jan Erik Schlorf Mar 09 '18 at 12:14

score 10 · Answer 2 · answered May 13 '15 at 22:40

Same problem for me was fixed by changing the line from:

./Pods/Fabric/Fabric.framework/run YOUR_API_KEY YOUR_BUILD_SECRET

to:

../Pods/Fabric/Fabric.framework/run YOUR_API_KEY YOUR_BUILD_SECRET

In other words, just prepend an extra '.' to designate that the 'Pods' directory is a sibling rather than a child of the build directory. YMMV.

score 9 · Answer 3 · answered Jun 30 '15 at 10:28

I had the same problem, use the $PODS_ROOT environment variable which points to your Pods folder; be sure to quote it in case you have spaces in your path; so instead of

./Pods/Fabric/Fabric.framework/run YOUR_API_KEY YOUR_BUILD_SECRET

use

"$PODS_ROOT"/Fabric/Fabric.framework/run YOUR_API_KEY YOUR_BUILD_SECRET

score 8 · Answer 4 · answered Nov 25 '15 at 03:12

8

Try:

Remove Fabric and Crashlytics in podfile.
pod install
Add Fabric and Crashlytics to podfile again
pod install
Add Run script like above answer.

Hope it help.

answered Nov 25 '15 at 03:12

eric long

640
5
16

score 7 · Answer 5 · answered Sep 21 '16 at 10:39

7

macOS Sierra, Swift 3

change

${PODS_ROOT}/Fabric/run

to

"${PODS_ROOT}/Fabric/run"

answered Sep 21 '16 at 10:39

Adam Smaka

5,977
3
50
55

brandonscript · Answer 6 · 2015-12-11T16:59:44.133

5

I had to use a different path in Xcode 7 using CocoaPods 0.39:

${SRCROOT}/Pods/Fabric/Fabric.framework/run <key> <secret>

podfile:

pod 'Crashlytics'
pod 'Fabric'

I also just updated Fabric to 3.4.1, and that path ^ changed slightly to Fabric/run. Make sure you check the bits after ${SRCROOT} carefully and compare it to what the Fabric app recommends. See the changelog for 3.4.1 for details.

edited Dec 11 '15 at 16:59

answered Sep 17 '15 at 00:09

brandonscript

68,675
32
163
220

I'm on Xcode 7.1 beta 1 and CocoaPods 0.39 and I still get the issue. Were you able to test this in a Xcode 7.1 beta? – Isuru Oct 24 '15 at 11:13
I haven't tried again on 7.1, but check the path in build settings nonetheless. – brandonscript Oct 24 '15 at 15:06

score 5 · Answer 7 · answered Mar 24 '16 at 08:30

5

in

Fabric (1.6.7)

You should change path from

"${PODS_ROOT}/Fabric/Fabric.framework/run" YOUR_API_KEY YOUR_BUILD_SECRET

to

"${PODS_ROOT}/Fabric/run"  YOUR_API_KEY YOUR_BUILD_SECRET

answered Mar 24 '16 at 08:30

UnRewa

2,462
2
29
31

score 3 · Answer 8 · answered May 08 '15 at 12:14

The path to the script that is executed during the build phase is different when you use Cocoapods. The github page on https://github.com/bpoplauschi/CrashlyticsFramework advises to use ./Pods/CrashlyticsFramework/Crashlytics.framework/run however, I found I had to use ./Pods/Fabric/Fabric.framework/run for my installation. Anyways you will have to dig through the Pods directory to find what you are looking for.

score 2 · Answer 9 · answered Jun 07 '18 at 09:20

If you update to Fabric & Crashlytics from older version:

If you have any data in your info.plist file by the key Fabric, make sure to delete all that info along with the key.
Use simple "${PODS_ROOT}/Fabric/run" script. Don't add any API_KEY and BUILD_SECRET

That worked for me, hope this helps.

score 1 · Answer 10 · answered Jul 16 '15 at 09:09

If you relied on something specific to the older Podspecs and can't update to the official libraries yet, you can add

source 'https://github.com/orta/FabricSpecs.git'
source 'https://github.com/CocoaPods/Specs.git'

To the top of your Podfile, and it will look for the older -unofficial- versions before the new ones. See the FabricSpecs repo for more details.

score 1 · Answer 11 · edited Sep 24 '16 at 09:44

1

For my project, this worked:

"${PODS_ROOT}/Fabric/Fabric.framework/run" YOUR_API_KEY YOUR_BUILD_SECRET

edited Sep 24 '16 at 09:44

Pang

9,564
146
81
122

answered May 18 '16 at 20:27

deepax11

199
3
7

1

how to know YOUR_API_KEY and YOUR_BUILD_SECRET ? – Moxarth Sep 27 '17 at 05:34

score 0 · Answer 12 · answered Mar 16 '15 at 07:25

Typically I would recommend not going against the grain and using the Fabric App for installation. Its hands down the simplest integration tool I've ever seen given the complexity they are providing.

That being said, since you're dead set on using Cocoapods, the only way to get things going would be the following

Run the Crashlytics App installer to the point where they give you the build phase script.
Copy the script
Undo the installation
Install via Cocoapods
Add the copied script to your buildphase

score 0 · Answer 13 · edited Jul 10 '15 at 03:11

0

I have meet this issue before. Here is my solution. to add the execution mode for the run file automatically before your run the script.

In the Build Phase -> Run Script add following line:

chmod +x ./Pods/CrashlyticsFramework/Crashlytics.framework/run

./Pods/CrashlyticsFramework/Crashlytics.framework/run YOUR_API_KEY YOUR_BUILD_SECRET

edited Jul 10 '15 at 03:11

Yurets

3,999
17
54
74

answered Jul 10 '15 at 02:22

StevenChen

43
1
8

Richard Grossman · Answer 14 · 2015-08-03T20:28:27.917

Delete podfile.lock and manifest.lock, then re-run podfile install, then continue from there using the "easy" configure app from Fabric.

There are some very nice screen-shot slide-show demos on Fabric.io's site. I found them with Google - don't see where they are accessible from the site.

FYI, if you're having issues, it's not you :). Basically (as of August 3rd), every step of the Fabric onboard process is potentially broken.

If you're lucky, you might have no issues.
If you're not, :( you might have issues to resolve at every step, including signing up for the service which can put you in an endless sign-up loop, and so on from there.

Hopefully these will all get fixed soon.

Warning: most of the answers you will find via a search will be outdated, because apparently fabric.io changed a lot on July 15th, but if you scroll down anything you find on stack/o, you might find a newer answer.

score 0 · Answer 15 · answered Apr 02 '18 at 00:51

0

Make sure to uninstall pod 'Answers', '~> 1.3' from your pods if you are using Fabric in your project before.

answered Apr 02 '18 at 00:51

Maximo Lucosi

378
4
9

score 0 · Answer 16 · answered Oct 17 '18 at 15:17

0

As mentioned in the official documentation, just update your pods repo

pod repo update

answered Oct 17 '18 at 15:17

Vitor Reis

487
6
11

Integrate Fabric/Crashlytics via CocoaPods

16 Answers16

Linked