{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 趁早两清 的问题《Crashlytics not deobfusticating code》','https://www.manongdao.com/q-764928.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
I'm new to Crashlytics, and I'm having a problem where it is not de-obfusticating my stack traces. According to Crashlytics this should be happening automatically. It should be using the mappings.txt file that's included in your .apk to decrypt the stack traces. I have a few questions about the whole process, as well as how I should go about solving the problem.
1) The mappings.txt file should be packaged with .apk by default correct? I'm using gradle; are there any options that you have to set?
2) I can't seem to download the stacktrace from Crashlytics, nor update the mappings.txt file on their dashboard. Are either of these options possible?
3) Can I get the stacktraces anywhere else, the application has GSM services enabled.
I had the same problem, but it seems to have been fixed by manually reinstalling the Crashlytics plugin.
Instructions at https://www.crashlytics.com/downloads/android-studio
(Using Android Studio 1.0 RC2)
EDIT: Crashlytics is now part of https://fabric.ioEDIT: Fabric is now part of https://firebase.google.com/docs/crashlytics/