crashlytics

I'm currently implementing the API Key switching script suggested here , except with build types instead of flavors. My build.gradle looks like this: ... buildTypes { debug { ... set("crashlyticsApiKey", "API_KEY_1") set("crashlyticsApiSecret", "API_SECRET_1") } release { ... set("crashlyticsApiKey", "API_KEY_2") set("crashlyticsApiSecret", "API_SECRET_2") } } ... productFlavors{...} ... File crashlyticsProperties = new File("${project.projectDir.absolutePath}/crashlytics.properties") applicationVariants.all { variant -> variant.productFlavors.each { flavor -> def variantSuffix = variant.name

I have a situation where I am trying to resolve these Crashlytics issues and I have this crash log Thread : Crashed: com.apple.main-thread 0 libobjc.A.dylib 0x34217f46 objc_msgSend + 5 1 UIKit 0x29a2d5a3 -[UIWebView webView:decidePolicyForNavigationAction:request:frame:decisionListener:] + 182 2 CoreFoundation 0x2630cad4 __invoking___ + 68 3 CoreFoundation 0x26239645 -[NSInvocation invoke] + 300 4 CoreFoundation 0x2623d0c7 -[NSInvocation invokeWithTarget:] + 50 5 WebKitLegacy 0x326d9261 -[_WebSafeForwarder forwardInvocation:] + 224 6 CoreFoundation 0x2630b62f ___forwarding___ + 354 7

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

Could not find method create() for arguments [crashlyticsStoreDeobsDebug, class com.crashlytics.tools.gradle.tasks.StoreMappingFileTask, com.android.build.gradle.internal.scope.BuildArtifactsHolder$FinalBuildableArtifact@2ac9ac29] on task set of type org.gradle.api.internal.tasks.DefaultTaskContainer. Project was in working state but since today build is failing with above error. Android Studio 3.2 Preview. maxoumime Update: Check Mike's answer first! Old answer: It looks like Fabric released a new version thats breaks the build for some apps. If you have the line io.fabric.tools:gradle:1.+

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

Crashlytics has been installed in the app in question for a couple of releases now. It's been working great. But as we prepare the next release Crashlytics has stopped reporting crashes in Release mode. Here are the things I can think of that have changed since our last release. Xcode 7.1. The last release was prepared with Xcode 6. We upgraded to Fabric. We're testing the app on iOS 9.1. Anyway, with all those changes crashes are still being reported just fine in Debug. Just not in Release (installing from TestFlight after archiving and uploading to iTunes Connect). Here are the things I've

The following error keeps coming up in my app's crashlytics logs on IOS 8: libobjc.A.dylib objc_msgSend + 5 didHideZoomSlider: Crashed: com.apple.main-thread EXC_BAD_ACCESS KERN_INVALID_ADDRESS at 0x0000000e I have no clue where to start? Anybody an idea on what I should be looking for? The whole stacktrace : 0 libobjc.A.dylib objc_msgSend + 5 didHideZoomSlider: 1 Foundation __NSFireDelayedPerform + 468 2 CoreFoundation __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 14 3 CoreFoundation __CFRunLoopDoTimer + 650 4 CoreFoundation __CFRunLoopRun + 1418 5 CoreFoundation

I'm trying to get logs with some service data with Crashlytics in my android application. But I don't see my logs in dashboard. I used this: String myLog = getServiceData(); //myLog is not null and non-empty CrashLytics.log(myLog); and this: String myLog = getServiceData(); //myLog is not null and non-empty CrashLytics.log(Log.Error, getString(R.string.app_name), myLog); I tried to generate exception in my application and handle it, but have no results: try { int a = 0; a = 1/a; } catch (Exception e) { CrashLytics.log(myLog); } Also I read on Crashlytics log not sent I need to initialize