twitter-fabric

When installing "Crashlytics" in my Android App, it automatically installs "Answers". I only want to install "Crashlytics" and want to have "Answers" disabled. Does anyone know how to do that? build.gradle dependencies { compile('com.crashlytics.sdk.android:crashlytics:2.5.5@aar') { transitive = true; } Thanks! Mike from Fabric and Crashlytics here. As you saw, Crashlytics by default includes Answers. If you don't want Answers enabled on your app, then you want to invoke CrashlyticsCore() when building your app instead of Crashlytics . For example, have these as your imports: import com

After upgrading from using the Crashlytics maven repo to the new Fabric maven repo and gradle plugin, my gradle builds have become incredibly slow. The problem seems to be caused by the Fabric maven repo returning a 401 unauthorized error whenever gradle tries to resolve a dependency: Failed to get resource: GET. [HTTP HTTP/1.1 401 Unauthorized: https://maven.fabric.io/repo/com/android/support/recyclerview-v7/maven-metadata.xml] Failed to get resource: GET. [HTTP HTTP/1.1 401 Unauthorized: https://maven.fabric.io/repo/com/android/support/appcompat-v7/maven-metadata.xml] Failed to get resource:

There is a Apps with Multiple Environments section in Fabric Crashlytics Advanced Setup that suggests to use a separate organization for each version. I have created 3 separate organizations per each Build configuration: MyApp MyApp (Debug) MyApp (AdHoc) I've got a conditional in my Run Script Build Phase that runs the Fabric framework script with different API Key s and Build Secret s and I can confirm that the conditional is being hit right, but I still do not get the API Keys updated in my plist (which I'm guessing Fabric uses). It seems like Fabric is sending my crashes to the last API key

I'm building an iOS app using React Native and trying to get it testable on phones. If I plug my phone into the computer and "build" directly to the phone, the app is built correctly and opens/operates correctly, no problem. But if I try to archive it and send it to phones using iTunes Connect's TestFlight or Fabric with Crashlytics, the app crashes immediately upon opening. It briefly shows the launch screen, but no more. Moreover, there are no crash reports -- in TestFlight, in Crashlytics, or in XCode, once I plug the phone back in. So I'm operating in the dark here, without any information

Looking for some help. I just upgraded my android app to fabric and now the app gives an error on this line: Crashlytics.start(getApplicationContext()); Gradle: error: cannot find symbol method start(Context) I tried commenting out that line, but then the crashes are not getting logged. How do I initialize Crashlytics in the new fabric framework? Am I missing something? Thanks in advance for your help. Cipriani Since Crashlytics is now part of Fabric the initialization process has changed, but is still simple. Instead of using Crashlytics.start() you should now use, but in the Application

I'm trying to upload a release to Fabric & I'm getting errors as follows. I'm using the XCode 6.3 (recently updated). XCode: 6.3 Fabric: 1.1.3 OSX: 10.10.3 What should I do to resolve above error & continue uploading the release via fabric desktop tool? Is there any other way to upload binary to fabric? Mike Bonnell Mike from Fabric here. 1) To clear that error from Fabric.app: Quit Fabric.app, then run this command to clear the local cache: rm -rf ~/Library/Caches/com.crashlytics.mac You may also need to clear: rm -rf ~/Library/Caches/com.crashlytics rm -rf ~/Library/Caches/com.crashlytics

I've recently started getting this error: 2015-03-23 11:35:48.902 run[60036:1047011] Crashlytics.framework/run 1.3.14 2015-03-23 11:35:48.911 run[60036:1047011] Crashlytics: dSYM Error Unable to process <your app>.app.dSYM at path /path/to/<your app>.app.dSYM Make sure your project build settings are generating a dSYM file. DEBUG_INFORMATION_FORMAT should be set to dwarf-with-dsym for all configurations. This could also be a timing issue, make sure the Crashlytics run script build phase is the last build phase and no other scripts have moved the dSYM from the location Xcode generated it.