proguard + crashlytics崩溃 [英] proguard + crashlytics crash

查看:95
本文介绍了proguard + crashlytics崩溃的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我已经在项目中集成了Crashlytics,现在,当我启用proguard时,应用程序崩溃.尝试将所有类从crashlytics中排除,但未成功

I have integrated Crashlytics in my project, Now when I enable proguard, App Crashes. Have tried to exclude all the classes from crashlytics with no success

文件proguard-rules.pro文件具有以下内容

File proguard-rules.pro file has the following

-keep class io.fabric.sdk.android.** { *; }
-keep interface io.fabric.sdk.android.** { *; }
-keep class com.digits.sdk.android.core.** { *; }
-keep interface com.digits.sdk.android.core.** { *; }
-keep class com.twitter.sdk.android.** { *; }
-keep interface com.twitter.sdk.android.** { *; }

-keep class io.fabric.** { *; }
-keep interface io.fabric.** { *; }
-keep class com.digits.** { *; }
-keep interface com.digits.** { *; }
-keep class com.twitter.** { *; }
-keep interface com.twitter.** { *; }
-keep class com.crashlytics.** { *; }
-keep interface com.crashlytics.** { *; }
-keep class com.crashlytics.** { *; }
-dontwarn com.crashlytics.**

我收到一个错误消息

com.example.app E/Answers: Failed to submit events task
    java.util.concurrent.RejectedExecutionException: Task java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@1d060ef0 rejected from java.util.concurrent.ScheduledThreadPoolExecutor@31c1ac69[Shutting down, pool size = 1, active threads = 0, queued tasks = 1, completed tasks = 9]
        at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2011)
        at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:793)
        at java.util.concurrent.ScheduledThreadPoolExecutor.delayedExecute(ScheduledThreadPoolExecutor.java:298)
        at java.util.concurrent.ScheduledThreadPoolExecutor.schedule(ScheduledThreadPoolExecutor.java:503)
        at java.util.concurrent.ScheduledThreadPoolExecutor.submit(ScheduledThreadPoolExecutor.java:602)
        at java.util.concurrent.Executors$DelegatedExecutorService.submit(Executors.java:593)
        at com.crashlytics.android.answers.AnswersEventsHandler.executeAsync(Unknown Source)
        at com.crashlytics.android.answers.AnswersEventsHandler.processEvent(Unknown Source)

我也查看了crashlytics文档,并尝试了所有可能的组合. 有人可以指导我吗

I have also looked at crashlytics document and tried every possible combinations. can someone please guide me on this

推荐答案

从他们的

首先,Fabric内部使用注释,因此添加以下内容 行到您的配置文件:

First of all, Fabric uses annotations internally, so add the following line to your configuration file:

-keepattributes *Annotation*

接下来,为了提供最有意义的崩溃报告,请添加 您的配置文件的以下行:

Next, in order to provide the most meaningful crash reports, add the following line to your configuration file:

-keepattributes SourceFile,LineNumberTable

如果您正在使用自定义例外,请添加此行,以便自定义 在混淆过程中会跳过异常类型:

If you are using custom exceptions, add this line so that custom exception types are skipped during obfuscation:

-keep public class * extends java.lang.Exception

这篇关于proguard + crashlytics崩溃的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆