Firebase-android-sdk: Firebase Crashlytics: failed for task ':news:uploadCrashlyticsMappingFileRelease'

[leotyndale]

Hello, our team has been unable to perform local packaging after using Firebase Crashlytics. Every time we start packaging, we will receive a prompt that Firebase failed to upload the mapping file, but our mapping file has not been generated yet, which causes this problem. It’s because FireBase uploads the mapping file too early. What should I do?

[google-oss-bot]

I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.

[leotyndale]

firebase Crashlytics Plugin Version :'2.1.1',
firebase Crashlytics Version : '17.0.1'

[KalaiSelvanG]

Any update on this issue?
FAILURE: Build failed with an exception.

• What went wrong:
  Execution failed for task ':APP:uploadCrashlyticsMappingFileRelease'.
  > Crashlytics could not find the resource file generated by Google Services. You may need to execute the :processGoogleServices Task. Please check your Firebase project configuration (https://firebase.google.com/docs/android/setup).

[leotyndale]

Hello, is there any progress on this question?

[KalaiSelvanG]

@leotyndale try add this on app gradle

gradle.taskGraph.whenReady {
tasks.each { task ->
if (task.name.contains("uploadCrashlyticsMappingFile")) {
task.enabled = false
}
}
}

[leotyndale]

@leotyndale try add this on app gradle

gradle.taskGraph.whenReady {
tasks.each { task ->
if (task.name.contains("uploadCrashlyticsMappingFile")) {
task.enabled = false
}
}
}

@KalaiSelvanG Thank you for your suggestion, but this may cause Firbase Crashlytics to fail to parse out the correct number of code lines and class name.

[KalaiSelvanG]

@leotyndale not sure about that will fail or not. As of now this is the one helps to me to assemble the release and I can able to see the reports with appropriate line numbers and class names

[leotyndale]

@KalaiSelvanG
Thank you, your code is very helpful and can solve my problem.
At the same time, I found another idea from other developers. #2057

I changed a part of the code and plan to try again.

afterEvaluate {
    Task uploadMappingTask = tasks.findByName("uploadCrashlyticsMappingFileRelease")
    if (uploadMappingTask != null) {
        println "find uploadMappingTask"
        Task packageTask = tasks.findByName("packageRelease")
        if (packageTask != null) {
            println "find packageTask"
            uploadMappingTask.mustRunAfter(packageTask)
        }
        Task packageBundleTask = tasks.findByName("packageReleaseBundle")
        if (packageBundleTask != null) {
            println "find packageBundleTask"
            uploadMappingTask.mustRunAfter(packageBundleTask)
        }
    }
}

[KalaiSelvanG]

@leotyndale did that worked?

[leotyndale]

@leotyndale did that worked?

@KalaiSelvanG Sorry I just saw, It's ok so far.

[harry248]

We get the same error since yesterday. Is this related to the Google Outage?

Execution failed for task ':app:uploadCrashlyticsMappingFileDevelopmentRelease'.
> java.io.IOException: Unknown error while sending file, check network [/Users/runner/work/1/s/app/build/crashlytics/DevelopmentRelease/mappings/6793dea943b640f9a460764e5d01ea54.gz; response: 500 HTTP/1.1 500 Internal Server Error]

[fallGamlet]

It's error may be when in Firebase Crashlytics not enabled for the project yet

[fallGamlet]

It's error may be when in Firebase Crashlytics not enabled for the project yet

After enable Crashlytics in Firebase project It's error is gone

[harry248]

It's error may be when in Firebase Crashlytics not enabled for the project yet

Nope. We didn't change anything at all and our builds are failing now. Other users are reporting the same issue (see https://github.com/firebase/firebase-android-sdk/issues/2234#issuecomment-745245491)

[fallGamlet]

It's error may be when in Firebase Crashlytics not enabled for the project yet

Nope. We didn't change anything at all and our builds are failing now. Other users are reporting the same issue (see #2234 (comment))

Just check the flag enabled on Crashlytics settings in Firebase project. For my case in my project app has been added long time ago, but Gradle build start throw error only from today

[harry248]

It's error may be when in Firebase Crashlytics not enabled for the project yet

Nope. We didn't change anything at all and our builds are failing now. Other users are reporting the same issue (see #2234 (comment))

Just check the flag enabled on Crashlytics settings in Firebase project. For my case in my project app has been added long time ago, but Gradle build start throw error only from today

You're right - we use flavor specific firebase projects and for that specific project Crashlytics indeed wasn't activated yet. That wasn't a problem until yesterday so maybe they just made it more verbose on their side.

[k-farhan]

It's error may be when in Firebase Crashlytics not enabled for the project yet

Nope. We didn't change anything at all and our builds are failing now. Other users are reporting the same issue (see #2234 (comment))

Just check the flag enabled on Crashlytics settings in Firebase project. For my case in my project app has been added long time ago, but Gradle build start throw error only from today

You're right - we use flavor specific firebase projects and for that specific project Crashlytics indeed wasn't activated yet. That wasn't a problem until yesterday so maybe they just made it more verbose on their side.

yeah, just checked. Apologies.