Gradle-play-publisher: Support for uploading Proguard mapping files

Created on 4 Mar 2016 · 13Comments · Source: Triple-T/gradle-play-publisher

In the Google Play developer console it's now possible to upload a Proguard De-obfuscation Mapping File for apps in order to have readable stacktraces. This is currently a manual step to be performend which requires a lot of administration (for each APK version a separate dedicated mapping file is needed). It would be great if the gradle-play-publisher task would upload the mapping file together with the APK automatically (in my opinion this would not require any end-user input configuration, since it's known if pro-guard has been used and where the generated files are located).

_update_ Please star this issue in order to make this possible: https://code.google.com/p/android/issues/detail?id=203432

enhancement help wanted

Source

peterhav

👍23

Most helpful comment

I have implemented it and added a pull request here:
https://github.com/Triple-T/gradle-play-publisher/pull/179

clhols on 25 Nov 2016

👍9

All 13 comments

This is a killer feature, managing those have always been a huge pain for me. Just storing somewhere all those multiple-Mb files is already a problem on it's own and one have to keep them up to date as well!

Alexander-- on 5 Mar 2016

We have to check if the API supports this. Unfortunately, I don't have time right now, but feel free to file a PR :)

@bhurling FYI

ChristianBecker on 11 Mar 2016

PR has been issued: https://code.google.com/p/android/issues/detail?id=203432

peterhav on 11 Mar 2016

👍1

radzio on 5 Apr 2016

Unfortunately we can't do anything without an API for this. So please star the referenced android issue ;)

ChristianBecker on 7 Apr 2016

Starred it. Would be very helpful, indeed.

bhurling on 12 Apr 2016

@Alexander-- In the meantime, you could store the mapping files as build artifacts in whatever CI you use. I know circleci support this, as I use this. Don't know about other ci providers.