Reputation: 2734
I have implemented Firebase
crashlytics
as suggested. I have put this in my app level release
build variant:
firebaseCrashlytics
{
mappingFileUploadEnabled true
}
but when I start to build signed apk
I am always getting this error
Task :app:uploadCrashlyticsMappingFileRelease FAILED
FAILURE: Build failed with an exception.
Expected file collection to contain exactly one file, however, it contains no files.
If I set mappingFileUploadEnabled
to false
then release apk
builds successfully. I have searched a lot but couldn't find a work around. Anyone can help?
Upvotes: 45
Views: 36279
Reputation: 712
In case you variant doesn't need fierbase crashlytics, just disable them below
flavorDimensions += "server"
productFlavors {
sdk31 {
dimension "server"
FirebasePerformance {
instrumentationEnabled false
}
firebaseCrashlytics {
mappingFileUploadEnabled = false
}
}
}
Upvotes: 1
Reputation: 722
For me it was Charles Proxy running in the background. The internet was working fine of the emulator, but building a release build threw that error. Closing Charles wasn't enough, I had to close Charles followed by restarting Android Studio which fixed the issue.
Upvotes: 0
Reputation: 41
In gradle-wrapper.properties adding the below block solved issue for me. Note: These properties should not be added to project level gradle.properties
systemProp.http.proxyHost=
systemProp.http.proxyPort=80
systemProp.https.proxyHost=
systemProp.https.proxyPort=80
Upvotes: 0
Reputation: 11
If you're working with GuardSquare's Dexguard solution. Order of your plugins should be,
plugins {
// Google Services Plugin
id 'com.google.gms.google-services'
// Firebase Crashlytics Plugin.
id 'com.google.firebase.crashlytics'
// Dexguard Plugin
id 'dexguard'
}
This way the uploading process of your mapping file is going to succeed.
Upvotes: 0
Reputation: 59
I have faced several times, and there is a different solution i have.
First of all: You need to open android module of that project.
Flutter -> Open Android module in Android Studio.
And then go to Gradle Scripts, find gradle.properties (Global properties) and remove this code
systemProp.http.proxyHost=
systemProp.https.proxyHost=
systemProp.https.proxyPort=80
systemProp.http.proxyPort=80
Upvotes: 0
Reputation: 3149
In my case, it was not adding com.google.gms:google-services
at all. The project is in Flutter and Flutter Firebase documents do not mention this.
Add these to android/build.gradle
(check the latest versions on the internet):
classpath 'com.google.gms:google-services:4.3.10'
classpath 'com.google.firebase:firebase-crashlytics-gradle:2.7.1'
Add these to at the very end of android/app/build.gradle
:
apply plugin: 'com.google.gms.google-services'
apply plugin: 'com.google.firebase.crashlytics'
For some reason, even if you have generated lib/firebase_options.dart
with flutterfire
, the plugin still wants google-services.json
file you have got from Firebase. Paste that file into android/app/
directory. And it builds for release.
Upvotes: 2
Reputation: 5925
Decreasing the version of the following
classpath "com.google.firebase:firebase-crashlytics-gradle:2.8.0"
to 2.6.0 solved my problem.
Upvotes: 3
Reputation: 2175
In my case I received the error because I wasn't connected to the internet. Fixed it by connecting to the internet and my build release worked perfectly for my Flutter App.
Upvotes: 13
Reputation: 422
Just change sequence of crashlytics, apply plugin as below :
// Put Google Service
apply plugin: 'com.google.gms.google-services'
// After that the Firebase Crashlytics plugin.
apply plugin: 'com.google.firebase.crashlytics'
Upvotes: 8
Reputation: 644
Error: "Crashlytics could not find Google Services plugin task: processReleaseGoogleServices. Make sure com.google.gms.google-services is applied BEFORE com.google.firebase.crashlytics. If you are not using the Google Services plugin, you must explicitly declare googleServicesResourceRoot inputs for Crashlytics upload tasks."
I had something like this in build.gradle
apply plugin: 'com.google.firebase.crashlytics'
apply plugin: 'com.google.gms.google-services'
changed it to this and voila! it works:
apply plugin: 'com.google.gms.google-services'
apply plugin: 'com.google.firebase.crashlytics'
Upvotes: 56
Reputation: 101
I have resolved this issue by moving the following line from bottom of the page to top in build gradle.
Previous Settings:
apply plugin: 'com.google.gms.google-services'
New Settings:
apply plugin: 'com.android.application'
apply plugin: 'com.google.gms.google-services'
apply plugin: 'com.google.firebase.crashlytics'
And the issue is resolved.
Upvotes: 10
Reputation: 301
I faced the same event today.The reason for this to happen is as follows.
If minify true is set, obfuscation will be applied at build time and mapping.txt will be created.
If minify false, it will not be obfuscated at build time and mapping.txt will not be created.
If you set mappingFileUploadEnabled true in the minify false state, the Firebase SDK will try to upload mapping.txt to Firebase even though mapping.txt is not created at build time. The result is an error.
So, if you set minify false, you have to set mappingFileUploadEnabled false, if you set minify true, you need to set mappingFileUploadEnabled true or false (when mappingFileUploadEnabled false, the crash log on Firebase was obfuscated. It may not make much sense as it will be displayed in state).
https://firebase.google.com/docs/crashlytics/upgrade-sdk?platform=android#firebase-crashlytics-sdk_7
https://developer.android.com/studio/build/shrink-code#enable
Upvotes: 30
Reputation: 27
Add this at the bottom of your build.gradle file
apply plugin: 'com.google.gms.google-services'
Upvotes: 1