In any androi dproject with the 'Google Play Service' library to use AdMob or any other,
Proguard 4.11 spit out below error. 4.10 is ok with same proguard script.
java.lang.IllegalArgumentException: Value is not a reference value [proguard.evaluation.value.InstructionOffsetValue]
at proguard.evaluation.value.Value.referenceValue(Value.java:97)
at proguard.optimize.evaluation.SimpleEnumUseSimplifier.isPoppingSimpleE
num(SimpleEnumUseSimplifier.java:530)
at proguard.optimize.evaluation.SimpleEnumUseSimplifier.isPoppingSimpleE
num(SimpleEnumUseSimplifier.java:520)
at proguard.optimize.evaluation.SimpleEnumUseSimplifier.visitVariableIns
truction(SimpleEnumUseSimplifier.java:229)
at proguard.classfile.instruction.VariableInstruction.accept(VariableIns
truction.java:306)
at proguard.optimize.evaluation.SimpleEnumUseSimplifier.visitCodeAttribu
te(SimpleEnumUseSimplifier.java:131)
at proguard.classfile.attribute.CodeAttribute.accept(CodeAttribute.java:
101)
at proguard.classfile.ProgramMethod.attributesAccept(ProgramMethod.java:
I can't reproduce the problem with ProGuard 4.11 (optimization enabled), the latest Google Play Services Rev.15, and its AdMob sample. I just added the following definitions to google_play_services/samples/admob/project.properties and used "ant release" to build the project:
Do you have a sample that does reproduce the problem? You can mail it to me if necessary.
You can probably work around the problem with the ProGuard option:
I'd very much prefer to fix it though.
Hi.
Please find attachment for your information. My configuration based on the
attchement. But I'm not sure that the attachement would be helpful since
without the optimization option of the config file also makes the
error.(Actually I do not understand what is what of cause... )
and FYI, same problem on the internet which posted article at '
http://stackoverflow.com/questions/22408811/why-ant-build-fails-with-proguard-enabled
'
which I got insight to solve the problem temporarily..
and another FYI at
'http://code.google.com/p/android/issues/detail?id=67544'
which I post. but google's answer. Pls refer that.
I hope that you can fix asap for the world.
Cheers.
On Mon, Mar 24, 2014 at 1:04 AM, Eric Lafortune lafortune@users.sf.netwrote:
Related
Bugs:
#505Please follow below steps then.
use Eclipse from Android.com as ADT included one and update ADT tool
manually since no auto update support for now.
'C:\adt-bundle-windows-x86_64-20131030\sdk\tools\proguard' the google
distribution binaries.
(it may the cause of the symtom??)
Please try it.
On Tue, Mar 25, 2014 at 2:18 AM, user091023097709 user080980990@users.sf.net wrote:
Related
Bugs:
#505This bug has now been fixed for the upcoming ProGuard 4.12 beta1.
Wow. you are great!.
Thank you for all your effort. I will keep being your loyal user.
On Tue, Apr 1, 2014 at 12:14 AM, Eric Lafortune lafortune@users.sf.netwrote:
Related
Bugs:
#505Chiming in here to report the same exception while optimizing an app using Google Play Services. Disabling the class/unboxing/enum did indeed workaround the problem, although I'm of course rather fond of all Proguard's optimizations!
Any prognosis for 4.12 (or the beta)?
So what's the first released version that is supposed to fix this? I'm still seeing this issue with Android Gradle plugin 1.3.1 / ProGuard 5.2.x.