bpoplauschi/crashlyticsframework

This contains the great Crashlytics Framework to be linked as a CocoaPod

crashlyticsframework's Issues

Unable to find a specification for `CrashlyticsFramework (~> 2.2)`

In my Podfile I have:
pod 'CrashlyticsFramework', '~> 2.2'

and doing apod install I receive the error:
Unable to find a specification for CrashlyticsFramework (~> 2.2)

Using the spec directly works:
pod 'CrashlyticsFramework', :podspec => 'https://raw.githubusercontent.com/bpoplauschi/CrashlyticsFramework/master/CrashlyticsFramework.podspec'

Looks like a CocoaPods bug but I figured I'll report it here in case anyone else runs into this. I am using CocoaPods 0.35.0.

Support for beta email group aliases

From this article:

http://support.crashlytics.com/knowledgebase/articles/370383-how-do-i-use-ios-build-servers-with-beta

It looks like passing in the -groupAliases as advertised from the above article doesn't work as expected. Output below:

2014-08-22 17:39:37.295 submit Crashlytics: Invalid argument provided, -groupAliases
2014-08-22 17:39:37.297 submit Crashlytics: Companion to the Crashlytics Mac App for submitting iOS builds for Beta Testing.
     Usage:
         submit  API_KEY BUILD_SECRET        default options for upload after archive, with ipa path in environment
         additional options:
          -help        display this message
          -ipaPath     [path to IPA]
          -emails      [tester email address],[email]
          -notesPath   [release notes]
          -debug        1                    enable debug logging

Auto linking warning when mixing Swift/Obj C in Xcode 6.

Auto-Linking supplied '/$ProjectPath/Crashlytics.framework/Crashlytics', framework linker option at /$ProjectPath/Qinec/Emma-iPad/Crashlytics.framework/Crashlytics is not a dylib - this warning occurs on Xcode 6 when you choose to use mixed mode Swift/Obj C code. Doesn't throw this warning until you try and add some Swift to an existing Obj C code base.

Upgrade to 3.0 SDK ?

Hi !
Seems Crashlytics released a new version of their SDK today. Could you make the update ?
Thanks,
Guillaume

Crashlytics for OSX

Crashlytics for OSX is out:

http://www.crashlytics.com/blog/announcing-crashlytics-for-os-x/

Are you planning to include it in your podspec? Thanks!

License not suitable for automatically displaying in apps?

Some apps which use Cocoapods automatically build a Settings bundle which displays all the LICENSE files from the pods in use, in an aggregated "Acknowledgements" section on the iOS Settings app. See our app, Seene, for an example of this.

Normally most of them are MIT, etc., quite short licenses. Since last updating the Crashlytics cocoapod, it became huge, as it seems to include the whole Terms & Conditions.

Are you sure you want this to be the license file on the repo? (which will be potentially facing the 3rd party users of apps which use Crashlytics through the cocoapod, such as Seene). One could argue that the Terms & Conditions is an agreement between Crashlytics and the maker of the app, and that there is no need to show it from a Crashlytics-enabled app to a third party user.

Apple Mach-O Linker Error "_OBJC_CLASS_$_Crashlytics", referenced from

Hi, I am using CocoaPods to add CrashlyticsFramework.
First, add run script ./Crashlytics.framework/run xxxxxx in Xcode. Compile and success. Check.
Add pod 'CrashlyticsFramework', '~> 2.2.2' in Podfile. Compile and success. Check.
Import <Crashlytics/Crashlytics.h>. Compile and success. Check.
Add code [Crashlytics startWithAPIKey:@"xxxxxx"];. Compile and Failed. Got these message:

Undefined symbols for architecture i386:
"OBJC_CLASS$_Crashlytics", referenced from:
objc-class-ref in AppDelegate.o
ld: symbol(s) not found for architecture i386
clang: error: linker command failed with exit code 1 (use -v to see invocation)

I check the Pods.xcconfig, where the search paths were in, and make sure they are all there. Adde it as the based-on config file. Add $(inherited) to target's search path.

So what did I miss? Could anyone help?

Solved:

By adding every item in Pods.xcconfig to Xcode target's settings. I only added search paths. In fact, other linker flag also needs the $(inherited). And that solve the problem.

Compile error

After adding the appropriate line to the Podfile and running pod update I'm getting the following error when I build the project:

ld: framework not found Crashlytics
clang: error: linker command failed with exit code 1 (use -v to see invocation)

At first I thought it might be related to the build phase script I've added, but even after I removed it completely I'm still getting that error.

Xcode 5

Linker warning in Xcode 6

We started getting this build warning after upgrading to Xcode 6:

Warning: Auto-Linking supplied 'Pods/CrashlyticsFramework/Crashlytics.framework/Crashlytics', framework linker option at Pods/CrashlyticsFramework/Crashlytics.framework/Crashlytics is not a dylib

Everything seems to work fine with Crashlytics, but it would be nice to not have that warning when we build. Any ideas?

Please add Fabric support

Crashlytics had been replaced by Fabirc, please support it, thx

Deprecate in favor of the new official pod

Fabric recently released Crashlytics, TwitterKit, Digits and Fabric as official pods on CocoaPods Trunk: https://cocoapods.org/owners/7558

This means that that seems now like their official distribution channel, or at least that they will maintain those pods regularly, so them being the official account, you should probably deprecate your pod in favor of theirs?

Crashlytics App Download Popup When Building

When I build my project I get this message. Anyway around this?

Upgrade to the latest > 2.2.1

Hello,

Could you please check if a new version of Crashlytics SDK was released. I see some new features added on my application dashboard, so I guess they are probably backed by a newer SDK release somehow.

Thanks.

Automatically add required Run Script section

http://stackoverflow.com/questions/20072937/add-run-script-build-phase-to-xcode-project-from-podspec

I am not a Ruby developer so it would take me a while to piece it together but with a little help it might be possible to include the required Run Script section for each of the build targets. (I typically have at least 2 or 3 build targets to support a Staging and Production target and sometimes a Mock target.)

What the Podspec could not include is the keys used by the run script. I do not know how a Podspec would specify a Run Script and take in local parameters for this purpose or if that is even supported with CocoaPods at the moment.

I'd like to help make this work if you'd like to collaborate on it.

Bad path for then `run` command

I found with a project I was just setting up that the usual path would not work. I figured out what had to change by echoing the pwd command from the script. I am not sure if a variable is set for the Pods folder, so maybe the PROJECT_DIR or another variable could be used to make project setup go a little more smoothly.

In my case I just needed to adjust the relative path up a folder.

echo `pwd`
../Pods/CrashlyticsFramework/Crashlytics.framework/run 1234 4567