crashlytics-android

问题 Is it possible to lazily initialize Fabric Kits? for example, right now I do: Fabric.with(this, crashlytics, twitterCore, tweetUi); // 500ms I would like to initialize only Crashlytics (no twitter stuff), like below, because it is 10x faster, and I don't need the Twitter stuff right away Fabric.with(this, crashlytics); // 50ms Later on, when the user visits an activity where I need TwitterCore & TweetUi, I'd like to add them to Fabric on the fly before using them. Is this possible ? Edit: I

问题 android.content.res.Resources$NotFoundException android.content.res.ResourcesImpl.getResourcePackageName After upgrading Crashlytics from 2.6.6 to 2.9.1 we have started to notice a crash in Google Play Console. This crash happens before Crashlytics is initialized so it is never reported in Crashlytics: java.lang.RuntimeException: at android.app.ActivityThread.installProvider (ActivityThread.java:6423) at android.app.ActivityThread.installContentProviders (ActivityThread.java:6012) at android

问题 I'm trying to automate my app build distribution via Jenkyns and Crashlytics. I configured all as indicated on the documentation but crashlyticsUploadDistributionRelease failed with this error: "Distribution upload failed" and "WARN - Crashlytics halted compilation because it can't distribute the unsigned APK:". how can I fix it ? 回答1: Mike from Fabric and Crashlytics here. Beta for Android only supports distributing a signed APK, unsigned APKs can't be distributed. For information on how to

问题 Closed. This question is off-topic. It is not currently accepting answers. Want to improve this question? Update the question so it's on-topic for Stack Overflow. Closed 2 years ago . After integrating Firebase Crashlytics instead of Firebase Crash Reporting I have begun to get some crashes. I don't know anything about com.google.android.gms.phenotype.provider.ConfigurationProvider . What is it? And it appears on some devices (e.g. Samsung S8) This is a stack trace: Fatal Exception: java.lang

问题 We're using Fabric / Crashlytics for sending non-crash issues to their servers and later checking out the logs and stacktraces. Unfortunately, the Crashlytics API requires to use a different Exception subclass instance for different issue types. (In the iOS SDK, you can simply use a string for different issue types, but in the Android version, you can't). public static void craslyticsRecordError(String issueType, String errorMsg) { Exception e = new Exception(issueType + "-" + errorMsg);

问题 I am trying to integrate firebase crashlytics in my app. But I am getting an exteption "Expected file collection to contain exactly one file, however, it contains no files". However it works fine with io.fabric.tools:gradle:1.25.4 . Any idea? I am using gradle wrapper- 5.1.1 Root - build.gradle dependencies { classpath "com.android.tools.build:gradle:3.4.1" classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:1.3.50" classpath 'io.fabric.tools:gradle:1.27.1' classpath 'com.google.gms:google

问题 I am working on an open-source project (Kotlin, Toothpick, Clean Architecture - nowadays hype themes, but that's not the question :). I am using Fabric's Crashlytics, so I hid the API and secret keys into fabric.properties , according to the the official docs (and here are some details) The question is what is the best way to provide some dummy keys to collaborators without needing to solve merge conflicts in this properties file? If I publish the project without this file, it will crash on

问题 I have a situation where I want to add some logs to Crashlystic for Android, but not always send it. Then before coming back to the same function I want to clear the log. For this I can't seem to find how to do this. Below is an illustration of the situation: public foo() { bar(); bar(); bar(); } public bar() { // Clear log here, but I don't know how ... // Add new log here. Crashlytics.log(1, "TAG", "log information"); Crashlytics.log(1, "TAG", "log information"); Crashlytics.log(1, "TAG",

问题 I'm using crashytics from Fabric.io in my app. Here's how I have initialised it in my MainActivity.java at the very last of onCreate() method: Fabric.with(this, new Crashlytics()); Here's build.gradle (Project: abc) file: // Top-level build file where you can add configuration options common to all sub-projects/modules. buildscript { repositories { mavenCentral() maven { url 'https://maven.fabric.io/public'} } dependencies { classpath 'com.android.tools.build:gradle:2.2.3' classpath 'com

问题 I am trying to ShadowClass Crashlytics/Fabric so that Robotlectric 3 tests do not fail. What I have so far is this: The custom test runner that adds the Shadow class for Fabric: public class TestRunner extends RobolectricGradleTestRunner { public TestRunner(Class<?> klass) throws InitializationError { super(klass); } @Override protected ShadowMap createShadowMap() { return super.createShadowMap() .newBuilder().addShadowClass(ShadowFabric.class).build(); } @Override public