Databases
StackOverflow2013
Postsdbo
POFailed to export application after upgrade to Proguard 4.8
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POFailed to export application after upgrade to Proguard 4.8
    primarykey
    data
    text
    <p>I just upgraded my Android SDK, ADT and Proguard to the latest and greatest. </p> <p>My project compiles builds and runs fine in debug mode, but as soon as I try to export a signed release APK of it, I receive an error from the Export Wizard <strong>without any error log messages on the Eclipse console!*</strong></p> <p><img src="https://i.stack.imgur.com/NGLpE.png" alt="enter image description here"></p> <p>If I try to view the error log via <code>Window-&gt;Show View-&gt;Error Log</code> all I see is more of the same:</p> <p><img src="https://i.stack.imgur.com/gHoJS.png" alt="enter image description here"></p> <p>I have no idea what to do because neither Eclipse nor Proguard would give <strong>any hint</strong> about what the problem could be.</p> <p>My project exported fine until this recent upgrade. No build warnings. No lint warnings!</p> <p>I am using the standard configuration file for Android in <code>${sdk.dir}\tools\proguard\proguard-android.txt</code>:</p> <pre><code>-dontusemixedcaseclassnames -dontskipnonpubliclibraryclasses -verbose -dontoptimize -dontpreverify -keepattributes *Annotation* -keep public class * extends android.app.Activity -keep public class * extends android.app.Application -keep public class * extends android.app.Service -keep public class * extends android.content.BroadcastReceiver -keep public class * extends android.content.ContentProvider -keep public class * extends android.app.backup.BackupAgent -keep public class * extends android.app.backup.BackupAgentHelper -keep public class * extends android.preference.Preference -keep public class * extends android.support.v4.app.Fragment -keep public class * extends android.app.Fragment -keep public class com.android.vending.licensing.ILicensingService -keepclasseswithmembernames class * { native &lt;methods&gt;; } -keep public class * extends android.view.View { public &lt;init&gt;(android.content.Context); public &lt;init&gt;(android.content.Context, android.util.AttributeSet); public &lt;init&gt;(android.content.Context, android.util.AttributeSet, int); public void set*(...); } -keepclasseswithmembers class * { public &lt;init&gt;(android.content.Context, android.util.AttributeSet); } -keepclasseswithmembers class * { public &lt;init&gt;(android.content.Context, android.util.AttributeSet, int); } -keepclassmembers class * extends android.app.Activity { public void *(android.view.View); } -keepclassmembers enum * { public static **[] values(); public static ** valueOf(java.lang.String); } -keep class * implements android.os.Parcelable { public static final android.os.Parcelable$Creator *; } -keepclassmembers class **.R$* { public static &lt;fields&gt;; } -dontwarn android.support.** </code></pre> <p>And my project's proguard.cfg only contains:</p> <pre><code>-assumenosideeffects class android.util.Log { public static *** v(...); public static *** i(...); public static *** d(...); public static *** w(...); public static *** e(...); } </code></pre> <p>Anyone seen this problem before? Any idea how to fix this?</p> <p><strong>Some progress?</strong> I was able to export a signed APK for the first time since I upgraded by doing this:</p> <ol> <li>I ran CCleaner to clean all temp files and caches in the Windows system, </li> <li>Then I rebooted Windows. </li> </ol> <p>But to my dismay, the next time I tried to export the signed APK again, I received the same <code>Failed to export application</code> with <strong>no console messages!</strong> Again! </p> <p>Now it's clear to me that the Android dev tools have become unstable. I can't really run CCleaner and reboot Windows every time I want to export a signed APK. And I don't care whose fault is it: Android SDK? ADT plugin? Proguard?</p> <p>What do I do now?</p> <p><strong>Some more progress?</strong> I tried exporting a signed APK with Proguard turned off. It exported OK but when I launch it, it immediately crashes for being unable to find the application's activity class (<code>ClassNotFoundException</code>). This is weird! It runs fine in debug mode and if the application's activity class weren't there, it shouldn't have compiled! What's going on? Are the latest &amp; greatest Android dev tools broken?</p> <p>I tried playing with the <code>Order and Export</code> tab as described in <a href="https://stackoverflow.com/a/9831061">this solution</a> (and <a href="https://stackoverflow.com/a/10866563">this one</a> too) but it didn't help.</p> <p>What do I do now?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USan00b
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POFailed to export application after upgrade to Proguard 4.8
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POFailed to export application after upgrade to Proguard 4.8
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POFailed to export application after upgrade to Proguard 4.8
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload