firebase-android-sdk: A problem was found with the configuration of task ':app:uploadCrashlyticsMappingFileRelease' (type 'UploadMappingFileTask'). - Type 'UploadMappingFileTask' property 'googleServicesResourceRoot' doesn't have a configured value.
After updating to classpath 'com.google.firebase:firebase-crashlytics-gradle:2.7.0'
A problem was found with the configuration of task ':app:uploadCrashlyticsMappingFileRelease' (type 'UploadMappingFileTask').
- Type 'UploadMappingFileTask' property 'googleServicesResourceRoot' doesn't have a configured value.
FAILURE: Build failed with an exception.
* What went wrong:
A problem was found with the configuration of task ':app:uploadCrashlyticsMappingFileRelease' (type 'UploadMappingFileTask').
- Type 'UploadMappingFileTask' property 'googleServicesResourceRoot' doesn't have a configured value.
Reason: This property isn't marked as optional and no value has been configured.
Possible solutions:
1. Assign a value to 'googleServicesResourceRoot'.
2. Mark property 'googleServicesResourceRoot' as optional.
Please refer to https://docs.gradle.org/7.0/userguide/validation_problems.html#value_not_set for more details about this problem.
I tried to read the documentation and changelog, however none of them help on how to fix the problem.
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 16
- Comments: 31 (3 by maintainers)
Found a fix for me. AS 4.2.1Buld May 10,2021 Gradle Plugin 4.2.1 Gradle Version 7.1 com.google.firebase:firebase-crashlytics-gradle:2.7.0
This produces the error
While this does not, note com.google.gms.google-services is now ABOVE com.google.firebase.crashlytics
When you update to com.google.firebase:firebase-crashlytics-gradle:2.7.0 and sync the changes with them in the wrong order you are given an message stating that is the fix.
Thanks, that worked. I now have:
The warning only shows up when you change and re-sync your gradle, it is also very easy to miss as it isn’t red text and if you don’t have the build window open it doesn’t auto open. I didn’t notice it until I went looking for a warning or error to see why my build was failing.
I can reproduce the warning without fail each time I put them in the wrong order and re-sync.
It happens on gradle 6.7.1 too
Hello, I’m affected as well since upgrading the Firebase Crashlytics Gradle plugin from 2.6.1 to 2.7.0.
Looks like that 2.7.0 version didn’t undergo end-to-end testing… I have no choice but to revert the upgrade.