firebase-android-sdk
firebase-android-sdk copied to clipboard
firebase
Manual upload the mapping file
What feature would you like to see?
The Firebase Crashlytics will auto upload the mapping file during the build phase, and I want to have the capability to upload it manually.
How would you use it?
Our build server will not allow to visit the external url, only allow to the local server, so it can't send the mapping file to the Google Firebase Server. If it will have the tools/tasks to support manual upload that will be really helpful.
I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.
Will this issue be take care of by Google, or just let it go? It will be appreciated that if someone can update the status or comment about it.
Hey folks we have are aware this is a desired feature and will be supporting it eventually. I don't have a timeline for it yet, though. I'll keep the issue open and we'll post an update here when we have one.
It's probably low priority from Google's perspective, but it's one blocker issue for our team, so do you have any workaround for it, or any tricky things can do it? Or any sample code I can refer if I want to build the "manual upload tool"? Really appreciate someone from the Firebase Android SDK team can give any hint.
`
| PUT /v1/project/-/app/app_id/upload/java/35387219eef244db825e995a8085xxxx HTTP/1.1 | |
|---|---|
| User-Agent | crashlytics-gradle/2.6.1 |
| X-CRASHLYTICS-API-CLIENT-TYPE | crashlytics-gradle |
| X-CRASHLYTICS-API-CLIENT-VERSION | 2.6.1 |
| Content-Length | 5208094 |
| Host | firebasecrashlyticssymbols.googleapis.com |
| Connection | Keep-Alive |
| Accept-Encoding | gzip,deflate |
This is the API called upload the mapping file, so probably we can call it and build the upload tool by ourself.
Hi there, any update for this?
My team follow this article https://medium.com/nerd-for-tech/secure-your-firebases-google-services-json-file-in-android-16680f8e5fb4 to secure our google keys, but somehow our crash report still obfuscate.
Anyone familiar with this?
Hello,
Does Firebase Console Crashlytics have any means to associate the mappings file uploaded during the build step to a specific app version? If not does it mean that uploading a new mappings file would break deobfuscation of stack traces generated by earlier versions?
Google Play provides the ability to upload a mapping file for a given app version which seems the proper thing to do.
@ptsekov The mapping file is associated with a UUID that is added to the app as a resource during compilation, not the app version code. So unless you've hardcoded that UUID, new builds will not overwrite old ones, even if the version code is the same.
As a general update, we have prioritized work on the manual (non-Gradle) mapping file upload utility. We don't have an ETA for release yet but it is being worked on.
Hi there, any update for this?
My team follow this article https://medium.com/nerd-for-tech/secure-your-firebases-google-services-json-file-in-android-16680f8e5fb4 to secure our google keys, but somehow our crash report still obfuscate.
Anyone familiar with this?
@adef145 I did something similar for my team. Do you have a workaround yet?
Hi there, any update for this? My team follow this article https://medium.com/nerd-for-tech/secure-your-firebases-google-services-json-file-in-android-16680f8e5fb4 to secure our google keys, but somehow our crash report still obfuscate. Anyone familiar with this?
@adef145 I did something similar for my team. Do you have a workaround yet?
@SirGoingFar Currently we ignore it and in parallel trying Sentry instead
Hi all, the capability to upload mapping files outside of Gradle is now available in the Firebase CLI. If you have any issues with this feature, please report them in the firebase-tools repo. Thank you!
Hi all, the capability to upload mapping files outside of Gradle is now available in the Firebase CLI. If you have any issues with this feature, please report them in the firebase-tools repo. Thank you!
Thanks @mrichards dan teams