问题描述
我们正在使用Crittercism来分析我们的应用程序，崩溃，但由于我们还可以使用DexGuard默认混淆选项，Crittercism无法与DexGuard产生的mappings.txt脱混淆踪迹。
We are using Crittercism to analyze our app-crashes, but since we also use DexGuard with default obfuscation-options, Crittercism is unable to de-obfuscate the stacktraces with the mappings.txt generated by DexGuard.
所以，我的问题很简单：
So, my question is simple:
如何禁用非ASCII字符DexGuard-混淆？
How can I disable Non-ASCII characters for DexGuard-obfuscation?
我们正在BTW使用摇篮，构建系统。
We are using the Gradle-buildsystem btw.
推荐答案
好奇是什么促使您认为禁用非ASCII字符会解决DexGuard混淆的踪迹的Crittercism的处理？据我所知，他们将需要使用的DexGuard的一部分ReTrace.jar不ProGuard的（对不起，我不知道是否有可能关闭非ASCII字符）
Curious what led you to think that disabling Non-ASCII characters would fix Crittercism's handling of DexGuard-obfuscated stacktraces? AFAIK they would need to use the ReTrace.jar that's part of DexGuard not ProGuard (sorry i don't know if it's possible to turn off Non-ASCII chars)
对我来说这似乎是与Crittercism的问题，请他们支持DexGuard？我问他们的支持团队（[email protected]）〜1年多以前关于DexGuard支持，它甚至不是他们的路线图。
To me this seems like an issue with Crittercism, do they support DexGuard? I asked their support team ([email protected]) ~1yr ago about DexGuard support and it wasn't even on their roadmap.
如果你不依赖于Crittercism我知道Crashlytics和Hockeyapp支持DexGuard（这是其中一个原因，我切换Crashlytics）。
If you're not tied to Crittercism I know Crashlytics and Hockeyapp support DexGuard (it was one of the reasons I switched Crashlytics).
更新的
update
随机24:42我今天对面。您可以覆盖DexGuard的默认混淆字典和定义ASCII字符仅
Randomly I came across this today. You can override DexGuard's default obfuscation dictionary and define ASCII only characters.
定义您的dexguard-project.txt
define in your dexguard-project.txt
-obfuscationdictionary dictionary.txt
-classobfuscationdictionary classdictionary.txt
这篇关于如何dexguard混淆禁用非ASCII字符？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！