Phil
Phil

Reputation: 583

App crashes on mobile device after using ProGuard

After successfully using ProGuard on my application, it crashes on the startup on my mobile device. I use standard configuration of proguard: ${sdk.dir}/tools/proguard/proguard-android.txt

And logcat says something like this: E/AndroidRuntime(13441): at packagename.q.doInBackground(Unknown Source)

And then some App crashed errors etc.

Why does it not find my Source in doInBackground? Its a simple AsyncTask. Can anyone help me?

Edit: whole log:

I/ActivityManager( 1604): Start proc myPackageName for activity myPackageName/.MainActivity: pid=13961 uid=10147 gids={3003} I/ActivityManager( 1604): Displayed myPackageName/.MainActivity: +744ms (total +1m41s749ms) E/AndroidRuntime(13961): at myPackageName.q.doInBackground(Unknown Source) E/EmbeddedLogger( 1604): App crashed! Process: myPackageName E/EmbeddedLogger( 1604): App crashed! Package: myPackageName v4 (1.2.1) E/EmbeddedLogger( 1604): Application Label: XxX W/ActivityManager( 1604): Force finishing activity myPackageName/.MainActivity E/WindowManager(13961): Activity myPackageName.MainActivity has leaked window com.android.internal.policy.impl.PhoneWindow$DecorView@40dcbed8 that was originally added here E/WindowManager(13961): android.view.WindowLeaked: Activity myPackageName.MainActivity has leaked window com.android.internal.policy.impl.PhoneWindow$DecorView@40dcbed8 that was originally added here E/WindowManager(13961): at myPackageName.MainActivity.b(Unknown Source) E/WindowManager(13961): at myPackageName.l.a(Unknown Source) I/ActivityManager( 1604): Process myPackageName (pid 13961) has died.

Upvotes: 2

Views: 922

Answers (1)

Phil
Phil

Reputation: 583

I solved it. The problem was that I'm using jsoup in this doInBackground just added

#Keep jsoup -keep public class org.jsoup.** { public *; }

to the configuration and it works well, thanks for all your help

Upvotes: 3

Related Questions