google-fabric

App version always 0.0(0) after upload to fabric beta

放肆的年华 提交于 2019-12-06 15:05:00
I have strange problem with app version in fabric beta. After executing task :app:crashlyticsUploadDistribution build uploaded successfully. Version name and version code are correct for build, but version in the list of uploaded builds is always 0.0(0).And after downloading, versions of this builds are correcting. Wrong versions displayed only on fabric. Update: For setting version name and code I'm using "com.gladed.androidgitversion" plugin : androidGitVersion { format '%tag%' } android { defaultConfig { applicationId "my_package" minSdkVersion 19 targetSdkVersion 25 multiDexEnabled true

What use instead of TaskInternal execute() at gradle-5.1.1?

你离开我真会死。 提交于 2019-12-06 11:15:09
My custom task at gradle-4.10.1 : task fabricUploadApkDevelop(group: "fabric", dependsOn: ['assembleDevDebug']) { doLast { //fabric gradle task `assembleRelease crashlyticsUploadDistributionDevDevelop` and options: def task = tasks.getByName("crashlyticsUploadDistributionDevDebug") task.ext.betaDistributionGroupAliases = "develop" task.ext.betaDistributionNotifications = true task.ext.betaDistributionReleaseNotesFilePath = "${project.rootDir}/app/build/outputs/apk/dev/debug/releaseNotes.txt" task.execute() } } But at gradle-5.1.1 : TaskInternal.execute() is removed, so now I can't run my task

Crashlytics WebHook for Slack is not working

守給你的承諾、 提交于 2019-12-06 07:27:31
I have successfully configured Crashlytics Webhook with Slack. I have also tested it with the Test Message given in Crashlytics console. Test message working fine. But, when I have an actual crash in Crashlytics, it is not getting triggered into the Slack. I don't know where is the issue. What am I doing wrong here? Mike from Fabric here. I responded over email, but will make the answer public as well. For this integration, you've set the impact level to 5 which means that only issues that are the most impactful will be mentioned in Slack. If you want to be notified of every new issue, set the

Crashlytics task cannot be added to gradle tasks

孤街醉人 提交于 2019-12-06 06:33:27
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 went wrong: Task 'crashlyticsUploadDistributionDebug' not found in root project 'MyProject'. * Try: Run

crashlyticsGenerateSymbolsRelease - GC overhead limit exceeded

主宰稳场 提交于 2019-12-06 04:15:47
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:compileDebugSources :woh:assembleDebug :woh:crashlyticsGenerateSymbolsDebug :woh:crashlyticsCacheSymbolsDebug

Fabric plugin incompatible with Gradle 4.4 +

本小妞迷上赌 提交于 2019-12-06 01:30:01
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

Log to Crashlytics with tag and priority without also sending to logcat

你离开我真会死。 提交于 2019-12-05 21:01:07
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

On iOS, how to disable popup that reminds new versions and updates in old versions from Crashlytics Beta

爷,独闯天下 提交于 2019-12-05 14:27:16
This is regarding the iOS Enterprise apps downloaded from Crashlytics Beta Platform. Whenever there're new versions uploaded, when the old apps are launched, there will be popup that reminds user of new versions and updates in Crashlytics Beta. This seems to be automatically added by Crashlytics Beta. Just want to ask, is it possible to disable the popup so that testers can keep using the old app to do regression test? We couldn't seem to be able to find any configurations or settings about this. Mike from Fabric here. There is not a way to disable that notification currently on a per version

Why does Fabric mac app opens automatically when project is running?

十年热恋 提交于 2019-12-05 12:36:06
As part of fabric integration I have installed Fabric mac app, I found that whenever I run the project(I am running iOS app through XCode), the Fabric app also gets launched automatically, My Questions are: Why it automatically launches when running project ? Is there a way I can stop this happening ? FYI: The same happens even when the app is running in simulator. Mike from Fabric here. It's an odd behavior that you're seeing and is most likely due to an old version of the Run Script. Years ago, the run script build phase required the Fabric app to be present in order to handle the actual

Firebase Crashlytics not working without Fabric API key

霸气de小男生 提交于 2019-12-05 05:12:16
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 network, it appeared that I'm getting 403 Unathorized from Crashlytics. However when I add the Fabric API