google-fabric

Crashlytics task cannot be added to gradle tasks

眉间皱痕 提交于 2019-12-23 00:25:13
问题 I installed Crashlytics plugin to Android Studio project, but the gradle task crashlyticsUploadDistributionDebug is not added to gradle tasks. How can I add to gradle tasks? Installing Crashlytics is successed, but the command below is failed. $ ./gradlew assembleDebug crashlyticsUploadDistributionDebug The Task.leftShift(Closure) method has been deprecated and is scheduled to be removed in Gradle 5.0. Please use Task.doLast(Action) instead. FAILURE: Build failed with an exception. * What

crashlyticsGenerateSymbolsRelease - GC overhead limit exceeded

喜欢而已 提交于 2019-12-22 18:35:34
问题 about week ago we has been successfully integrate crashlytics in our cocos2d-x c++ project (ndk 14b). Everything looks fine, but about few days ago task crashlyticsUploadSymbolsRelease starts throw this error: Execution failed for task ':woh:crashlyticsGenerateSymbolsRelease'. > GC overhead limit exceeded javaMaxHeapSize "4g", javaMaxHeapSize "16g", org.gradle.jvmargs=-Xmx4096m, and so on doesn't help us. But crashlyticsUploadSymbolsDebug is working fine: :woh:assembleX86Debug :woh

Getting error “The package appears to be corrupt” in Fabric Beta on Android 6

﹥>﹥吖頭↗ 提交于 2019-12-22 06:43:03
问题 All my beta testers with Android 6 get this error when installing my app from Beta: App not installed. The package appears to be corrupt No problems for users with Android 7+. The APK can be dirrectly installed on all devices, including those with error in Beta. The problem appeared a few days ago, configuration of project did not change. All my users uses latest 1.7.0 Beta app. Project dependencies: dependencies { classpath 'io.fabric.tools:gradle:1.+' } compile('com.crashlytics.sdk.android

Firebase Crashlytics not working without Fabric API key

北战南征 提交于 2019-12-22 04:09:31
问题 I got an android app where Fabric Crashytics is installed. I've followed the official guide to setup Firebase Crashlytics and linked the Fabric and Firebase accounts (AFAIK Firebase acquired Fabric recently). So in particular I removed the Fabric API key with <meta-data/> tag in manifest.xml . Then I tried to make a test crash but it didn't appear neither in Firebase not Fabric dashboard, however I got a success log in logcat: Crashlytics report upload complete: <ID> . When I sniffed the

Crashlytics asks for dSYMs with UUIDs that don't match my app

↘锁芯ラ 提交于 2019-12-22 04:05:39
问题 I uploaded a new version 1.1 of my app to iTunesConnect and caused a couple of test crashes with Crashlytics . I added, via the Upload Symbols Script, the dSYMs that I downloaded from iTunesConnect since I had Enable Bitcode set to YES . The problem is that the 6 dSYM files that I uploaded do not match the UUID 's that Fabric requests. It asks for 2 separate UUIDs and neither match. My dSYMs downloaded from iTunesConnect : Note that version 1.0 was NOT uploaded with Enable Bitcode set to YES

Crashlytics asks for dSYMs with UUIDs that don't match my app

孤者浪人 提交于 2019-12-22 04:05:02
问题 I uploaded a new version 1.1 of my app to iTunesConnect and caused a couple of test crashes with Crashlytics . I added, via the Upload Symbols Script, the dSYMs that I downloaded from iTunesConnect since I had Enable Bitcode set to YES . The problem is that the 6 dSYM files that I uploaded do not match the UUID 's that Fabric requests. It asks for 2 separate UUIDs and neither match. My dSYMs downloaded from iTunesConnect : Note that version 1.0 was NOT uploaded with Enable Bitcode set to YES

Lazy initialization of Fabric kits?

落花浮王杯 提交于 2019-12-22 02:30:33
问题 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

Bogus NDK stack backtrace after upgrading to Crashlytics NDK 2.+

落花浮王杯 提交于 2019-12-21 17:28:30
问题 Looking for fabric support on an unwinding issue in the NDK stack trace after migrating from Crashlytics (2.6.8)/Crashlytics NDK (1.1.5) to Crashlytics (2.8.0)/Crashlytics NDK (2.0.0) and any newer versions after that. The stack trace we get prior to upgrading the libraries looked OK but after there a lot of missing symbols and the addresses jump wildly within and outside the application libraries. We've seen addresses jump hundreds of megabytes in address space from one frame to the next. So

Using Firebase Crashlytics and Fabric Answers

六月ゝ 毕业季﹏ 提交于 2019-12-21 11:14:10
问题 I would like to use Firebase Crashlytics and Fabric Answers together. According to this link, in order to setup Fabric Answers, we need to include Fabric API key. This link doesn't mention any need for Fabric API key for implementing Firebase Crashlytics. After some test, I found out that Firebase Crashlytics only works without Fabric API key in AndroidManifest as mentioned in this part of the documentation. On the other hand, Fabric Answers only works with Fabric API key in AndroidManifest.

Unlink an existing firebase app?

人走茶凉 提交于 2019-12-21 07:29:25
问题 I want to "Link to new or existing Firebase project & app" but the crashlytics dashboard told me my project is already linked, how to unlink my existing project ? 回答1: To unlink your Fabric app from Firebase, follow the following steps: Go to The Firebase project settings Go to Integrations Select the Fabric "Manage" link Click the "Unlink Fabric App" 回答2: Very late but if someone still having this problem: 1- try to unlink on firebase dashboard as explanined in this response: https:/