Mobclix And Proguard
Solution 1:
The messages explain that some Mobclix classes (like com.mobclix.android.sdk.MobclixContactsCursorEntityIterator
) depend on Android runtime classes (like android.content.Entity
) that are not present in your input jars or library jars. In general, that could be a sign of serious problems: if that part of the code is ever executed, it will fail with NoClassDefFoundError (even without obfuscation).
It looks like the Entity class has been introduced in Android SDK 7, so I presume that you are building against an older SDK. Again assuming that your code runs fine in spite of this missing class, you can let ProGuard accept the somewhat inconsistent input with
-dontwarn android.content.Entity*
Note that -keep options don't come into play here. ProGuard performs the consistency checks before considering any -keep options.
Also see ProGuard manual > Troubleshooting > Warning: can't find referenced class
Solution 2:
Maybe change
-keep publicclasscom.mobclix.android.sdk.*
to
-keep publicclasscom.mobclix.android.sdk.**
Post a Comment for "Mobclix And Proguard"