crashlytics

I have a project with multiple modules. The common code of the modules is in a library module. The problem is that we added recently Crashlytics to our project (in the library module), and we keep receiving error reports even when we are in Debug mode. I searched on the internet and I found out that a library is always seen as a Release mode. Now my question is, is there a way to disable Crashlytics in my case? Thanks In my app (a single module, multiple flavors), I detect the flavor, and only initialize Crashlytics in the flavors that I want. In my case, I add a variable to the flavor in

I followed setting up plugin to integrate crashlytics from this link https://www.crashlytics.com/onboard From eclipse, I logged into my fabric account and selected my project. Plugin made necessary changes to manifest and launch activity. It asked to build & run my app to complete step 1. But I am getting - ../kit-libs/com-crashlytics-sdk-android_crashlytics/bin(missing) ../kit-libs/com-crashlytics-sdk-android_crashlytics-core/bin(missing) ../kit-libs/com-crashlytics-sdk-android_beta/bin(missing) ../kit-libs/com-crashlytics-sdk-android_answers/bin(missing) ../kit-libs/io-fabric-sdk-android

Recently I have had to update my project to use Gradle 4.4 from 4.1. i.e. distributionUrl=https\://services.gradle.org/distributions/gradle-4.4-all.zip in my gradle-wrapper.properties file. However, this is incompabitble with the fabric plugin apply plugin: 'io.fabric' As since the gradle update, I now get build errors when syncing my project. Such as: Error:Could not get unknown property 'manifestFile' for task ':Module:generateVariantFlavorRFile' of type com.android.build.gradle.internal.res.GenerateLibraryRFileTask. Does anyone know when/if there will be a new plugin update that is

I have been trying to build the application which uses crashlytics from fabric.io. But build gets failed with bellow mentioned error. Executing tasks: [clean, :app:generateDebugSources, :app:generateDebugAndroidTestSources] Configuration on demand is an incubating feature. FAILURE: Build failed with an exception. * What went wrong: A problem occurred configuring project ':app'. > Could not resolve all dependencies for configuration ':app:classpath'. > Could not resolve io.fabric.tools:gradle:1.+. Required by: TestProject18July2016:app:unspecified > Could not resolve io.fabric.tools:gradle:1.+.

I've created OOM crashes by growing an infinitely large NSArray of NSStrings, and I've even tried calling exit(0) just to make it look like an OOM. While these things to have worked to terminate the app unexpectedly, I don't see any OOMs reported on Crashlytics and it doesn't call the delegate callback, crashlyticsDidDetectReportForLastExecution: , on the next run of the app. I'm running the app on a real device that is not connected to a simulator, and any other kind of crash/error it reports fine. Does anyone have any idea what the issue might be? Mike from Fabric here. We chatted over

There are two ways to log to Crashlytics according to the documentation . Crashlytics.log(int priority, String tag, String msg); In addition to writing to the next crash report, it will also write to the LogCat using android.util.Log.println(priority, tag, msg) . Crashlytics.log(msg); which will only write to the Crashlytics crash report [not logcat]. However, this second method does not allow me to set a tag and priority. Instead it automatically sets the resulting tag as "CrashlyticsCore" and priority to debug: From Fabric dashboard: 1 | 04:24:55:100 (UTC) | D/CrashlyticsCore ... 2 | 04:24

I am building an android library that I plan to integrate into many 3rd party apps(which do not belong to me). So, I am trying to figure out a way to find out if any of those 3rd party apps crashes due to the code in my library. Is there any way to find that out? I was looking at Crashlytics to achieve the same. But, as I understand, Crashlytics will be able to give the Crash analytics to only the app owner, right? Is there any way to collect the crash info without the intervention of the 3rd party app? Thanks. EDIT: This isn't a duplicate of Integrating Crashlytics to library project because

I have an iMessage extension within my iOS app. Can Crashlytics capture its crashes? I've tried adding the same Fabric entry from my main app's Info.plist into my iMessage extension's Info.plist , and adding the following to my MSMessagesAppViewController subclass (as recommended for Today widget intregation ): - (instancetype _Nonnull)initWithNibName:(NSString * _Nullable)nibNameOrNil bundle:(NSBundle * _Nullable)nibBundleOrNil { self = [super initWithNibName:nibNameOrNil bundle:nibBundleOrNil]; if (self) { // Start up Answers and Crashlytics [Fabric with:[NSArray<id> arrayWithObjects:

I am using Crashlytics to detect the crashes in my app. I occasionally get the follow crash report. The key crash point is -[NSObject(NSObject) doesNotRecognizeSelector:] and MyViewController.m line 596 -[MyViewController prepareForSegue:sender:]. I don't know what's the problem of that from the log. Is is possible a multi-threading issue? I am also using Parse SDK to retrieve the data from Parse cloud. And prepareForSegue:sender: method will be invoked when the user tap the disclosure indicator, it should run in main thread. Would you please give me some hint to troubleshoot this issue.