proguard

Is there an explicit way to stop ProGuard from changing a class from implementing an interface? I have a class that implements java.io.Serializable , let's call it com.my.package.name.Foo . I've found that after running through ProGuard, it no longer implements Serializable . I get null after I cast from Serializable to Foo and false if I check an instance with instanceof Serializable . I've made sure to set ProGuard to ignore this class: -keep class com.my.package.name.Foo I've also tried: -keep class com.my.package.name.Foo { *; } and I've also tried the whole package by doing this: -keep

I am using a third party library in my project, since then proguard is issuing me these warnings, which I can't relate to that library, Here is the library I am using: Lollipin . Warnings I am getting Warning:android.databinding.DataBindingUtil: can't find referenced class android.databinding.DataBinderMapper Warning:android.databinding.ViewDataBinding: can't find referenced class android.databinding.DataBinderMapper Warning:there were 43 unresolved references to classes or interfaces. Warning:Exception while processing task java.io.IOException: Please correct the above warnings first. What I

Hi I developed one android library and Now I want to obfuscate it for redistribution. I develop my library with eclipse and android version 4.1.2. I tried obfuscating with eclipse and pro-guard. I do export and and also put proguard.config = proguard-project.text in project-properties but it not generating any jar file. It shows me result as its not allowing to library projects. So I don't know how to obfuscating android library project. I need help regarding how to obfuscating of android library projects. Need Help Thank you. The Android SDK doesn't apply ProGuard to library projects; it only

I am trying to prevent proguard from obfuscating interface (or abstract class) methods parameters. Lets say I have this interface in my lib : package com.mypackage; public interface MyLibListener { void onSomething(boolean success, String message); } And this proguard file : -keepparameternames -keep interface com.mypackage.MyLibListener { *; } Then I assemble release and I get : package com.mypackage; public interface MyLibListener { void onSomething(boolean var1, String var2); } Same thing with abstract classes or using @Keep annotations. Obfuscation option keepparameternames seems to work

I am unable to generate Signed APK using minifyEnabled true and shrinkResources true App Level : build.gradle buildscript { repositories { mavenCentral() } dependencies { classpath 'com.android.tools.build:gradle:2.1.0' } } apply plugin: 'com.android.application' repositories { mavenCentral() } android { compileSdkVersion 23 buildToolsVersion '22.0.1' defaultConfig { applicationId "......." minSdkVersion 14 targetSdkVersion 21 versionCode 1 versionName "1.0" testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner" } buildTypes { debug { minifyEnabled true shrinkResources true

在Android开发中,屏幕适配是一个非常头痛的问题,因而为了去进行屏幕适配,作为程序员,是呕心沥血,历经磨难,哈哈 我们之前做屏幕适配一般都会用到一下两种方式: 我们之前做屏幕适配一般都会用到一下两种方式: 第一种就是宽高限定符适配，什么是宽高限定符适配呢 ├── src/main │ ├── res │ ├── ├──values │ ├── ├──values-800x480 │ ├── ├──values-860x540 │ ├── ├──values-1024x600 │ ├── ├──values-1024x768 │ ├── ├──... │ ├── ├──values-2560x1440 就是这种，在资源文件下生成不同分辨率的资源文件，然后在布局文件中引用对应的 dimens，大家一定还有印象 第二种就是 鸿神 的AndroidAutoLayout 这两种方案都已经逐渐退出了历史的舞台，为什么想必大家都知道，不知道的建议看看 拉丁吴 老师的文章，现在最主流的两种屏幕适配方案，今日头条适配方案和 smallestWidth 限定符适配方案,下面介绍一个框架,采用的是今日头条适配方案传送门 框架使用效果 Pixel 2 XL | 1440 x 2880 | 560dpi: Pixel XL | 1440 x 2560 | 560dpi: Nexus 5X | 1080