proguard

The crashlytics knowledge base says : "When building for release with Eclipse, export your application to an APK using the “Export Crashlytics-enabled Android Application” exporter from the Eclipse export menu." But I couldn't find this option. Here's the link Any help would be appreciated. Thanks! Never mind I found it. It's in File-> Export and under the Android folder, there's a new "Export Crashlytics-enabled Android Application" option. Had a habit of exporting the other way so never looked here before. 来源： https://stackoverflow.com/questions/18156701/how-to-export-signed-application

before adding google-play-services to my project its size was just 900kb and after adding lib of play services it is now 4.01MB . its terrible. for 900kb app ads of 3MB is too much. help me as soon as possible. my app is finished now. I tried reading about proguard but unable to understand. someone please give me step by step tutorial to reduce app size. Pranit More You don't need to edit google-play-services.jar file. Use proguard to keep only needed class files. Create proguard.txt file in your module directory (e.g. app/) and write following lines in that file: -keep public class com.google

I have generated an APK of my Android application (as a try) and I did not have any problem, the APK has been generated correctly. Now, I want to obfuscate my code while generating the APK so I used the following line on my release block on build.gradle file. minifyEnabled true The problem is that now it throws me the following error: Error:Execution failed for task ':app:transformClassesAndResourcesWithProguardForRelease'. java.io.IOException: Please correct the above warnings first. with a lot of warnings. To be more exact, 1018 warnings. Most of them are like: Warning:com.itextpdf.text.pdf

I'm trying to pack my project to APK and then obfuscate it with ProGuard. Here is my pom: <?xml version="1.0" encoding="UTF-8"?> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"> <modelVersion>4.0.0</modelVersion> <groupId>com.skayred</groupId> <artifactId>skayred</artifactId> <version>1.26</version> <packaging>apk</packaging> <name>skayred</name> <properties> <environment>development</environment> </properties> <dependencies> <dependency>

I've written an Android application using an Android Library project, also written by me. I have to release the source code of the app, but I don't want to distribute the sources of the library. This library defines, among other things, custom views, so it includes XML layouts and resources. I was thinking of releasing this library in binary form (a .jar maybe?), to be referenced by the main project. I want this binary library to be obfuscated via Proguard. Is this feasible? How? Thanks. As mentioned by Morrison Chang, there currently isn't any way to release an android library project as a

Intro: I have in AS 1 project with 2 models: Android library project with some "Public API class" Android APP dependent on above library (the library module is on the dependency list) Task: I want to obfuscate my library project because I want to expose it as public SDK but keep my code protected... What I did: So I made custom ProGuard rules: -dontshrink -dontoptimize -dontpreverify -keep class com.org.my_public_api_class_name I skip all other stages in order to eliminate where the bug is to only obfuscation stage. Result: Build of the APP module fails with errors like Error: cannot find

Can anyone give me any clues on how to debug the following. I have a mixed java / scala android project that I'm working on in Intellij and I process it through Proguard as part of run config. When I run the app I get the error: 07-24 12:36:35.879 21731-21779/com.ovaphone E/AndroidRuntime﹕ FATAL EXCEPTION: AsyncTask #1 java.lang.RuntimeException: An error occured while executing doInBackground() at android.os.AsyncTask$3.done(AsyncTask.java:299) at java.util.concurrent.FutureTask$Sync.innerSetException(FutureTask.java:273) at java.util.concurrent.FutureTask.setException(FutureTask.java:124) at