Closed wezley98 closed 3 years ago
Also worth mentioning that the same Firebase versions worked correctly with AS v4.0.1 and gradle-play-publisher
v2.8.0, and the mapping files were uploaded correctly.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Ah, sorry for not replying. This plugin has nothing to do with crashlytics, so you'd have to set up the wiring yourself. That said, I think this it's a decent feature request that wouldn't be too hard to implement.
Sorry, but why using bundleRelease
works but publishReleaseBundle
? Which means v3 broke original release flow. Does it means that we have to call uploadCrashlyticsMappingFileRelease
manually in v3?
We never did anything with crashlytics. I'm guessing you have something manual configured in your build files using the old task names.
@SUPERCILEX I didn't do anything special and the difference is clearly by executing ./gradlew --dry-run bundleRelease
v.s. ./gradlew --dry-run publishReleaseBundle
to any sample. The later one doesn't execute uploadCrashlyticsMappingFileRelease
.
Maybe the crashlytics plugin sets that up for you? We're using new APIs which means that task doesn't run AFAIK.
I've also hit this. I'm not 100% sure, but I think the Crashlytics plugin is hooking up their uploadCrashlyticsMappingFileRelease
task to depend explicitly on bundleRelease
. Since bundleRelease
is no longer run by publishReleaseBundle
, the mapping task isn't being run, so it's not being uploaded.
Easy workaround for now, just call both when publishing: ./gradlew bundleRelease publishRelease
You could also probably hook it this up automatically in Gradle, but that feels overkill.
Currently my workaround is gradlew publishReleaseBundle uploadCrashlyticsMappingFileRelease
I get an issue with the process uploadCrashlyticsMappingFileRelease
not completing at all. I just use the normal assembleRelease
command (not even publishing it).
android tools plugin version: 3.5.3
kotlin version: 1.4.10
gradle-wrapper: 6.6.1
crashlytics plugin: com.google.firebase:firebase-crashlytics-gradle:2.1.0
could the version of crashlytics be a reason why this is happening?
Currently my workaround is
gradlew publishReleaseBundle uploadCrashlyticsMappingFileRelease
Thanks, it helps
Same issue here, firebase crashreports are incomplete. Will try to use the workaround for now.
Just an addition to this
~/workspace/app [master]:$ ./gradlew --dry-run assembleRelease | grep rash
:app:injectCrashlyticsMappingFileIdRelease SKIPPED
:app:uploadCrashlyticsMappingFileRelease SKIPPED
~/workspace/app [master]:$ ./gradlew --dry-run publishReleaseApk | grep rash
:app:injectCrashlyticsMappingFileIdRelease SKIPPED
~/workspace/app [master]:$
Can someone confirm that this is fixed? I still dont see the upload task in /gradlew --dry-run publishRelease
Have you tried to update v3.2.0? @nicandris
I didnt push a release yet, but i updated to 3.2.0 now and:
$ ./gradlew --dry-run assembleRelease | grep rash
:app:injectCrashlyticsMappingFileIdRelease SKIPPED
:app:uploadCrashlyticsMappingFileRelease SKIPPED
$ ./gradlew --dry-run publishRelease | grep rash
:app:injectCrashlyticsMappingFileIdRelease SKIPPED
$
I've also update the v3.2.0 and also use manual task for now
Does the same thing happen if you run publishApk directly?
Describe the bug
Been seeing this for a while in v3.0 Snapshots, but just thought it was something to do with my build. Looked into it in more detail, and found the the
uploadCrashlyticsMappingFileRelease
isn't ran when running thepublishReleaseBundle
task.I'm not sure if this is an issue with AGP/Crashlytics plugin or that with the new Crashlytics plugin we now need to explicitly run the new mapping task.
Generating a bundle directly from Android Studio
Build -> Generate Signed Bundle / APK
correctly runs theuploadCrashlyticsMappingFileRelease
task as shown in the build logs below.How To Reproduce
publishReleaseBundle
task.Versions
Tasks executed
publishReleaseBundle
Expected behavior
Bundle is created and uploaded, Firebase mapping file is uploaded.
Additional context (if a crash, provide stack trace)
Further investigation shows that creating an App Bundle directly from Android Studio runs the following tasks automatically
Using
publishReleaseBundle
taskExample crash report for version above (836)