Dx fails with RoboGuice?

It turns out that this problem is related to Dalvik's hard 64k method limit I have filed a new bug report asking the Android team to fix the poor diagnostic output.

Up vote 0 down vote favorite share g+ share fb share tw.

I'm trying to package an Android app which uses RoboGuice. The . Class files compile fine, but when building the Android package, dx fails with a "No expanded opcode" message.

Running dx --dex --debug --verbose target/android-classes produces: trouble writing output: com.android.dx.util. DexException: No expanded opcode for 6c80c7f5 Key. Java:371@0003: invoke-virtual v0:Lcom/google/inject/Key$NullAnnotationStrategy;, com.google.inject.

Key$NullAnnotationStrategy. Clone:()Ljava/lang/Object; at com.android.dx.dex.code.OutputFinisher. FindExpandedOpcodeForInsn(OutputFinisher.

Java:526) at com.android.dx.dex.code.OutputFinisher. CalculateReservedCount(OutputFinisher. Java:467) at com.android.dx.dex.code.OutputFinisher.

ReserveRegisters(OutputFinisher. Java:403) at com.android.dx.dex.code.OutputFinisher. FinishProcessingAndGetList(OutputFinisher.

Java:359) at com.android.dx.dex.code.DalvCode. FinishProcessingIfNecessary(DalvCode. Java:108) at com.android.dx.dex.code.DalvCode.

GetInsns(DalvCode. Java:185) at com.android.dx.dex.file.CodeItem. Place0(CodeItem.

Java:223) at com.android.dx.dex.file.OffsettedItem. Place(OffsettedItem. Java:242) at com.android.dx.dex.file.

MixedItemSection. PlaceItems(MixedItemSection. Java:312) at com.android.dx.dex.file.DexFile.

ToDex0(DexFile. Java:543) at com.android.dx.dex.file.DexFile. ToDex(DexFile.

Java:216) at com.android.dx.command.dexer.Main. WriteDex(Main. Java:574) at com.android.dx.command.dexer.Main.

Run(Main. Java:218) at com.android.dx.command.dexer.Main. Main(Main.

Java:174) at com.android.dx.command.Main. Main(Main. Java:95) ...while placing CodeItem{com.google.inject.

Key$NullAnnotationStrategy. Values:()Lcom/google/inject/Key$NullAnnotationStrategy;} ...while writing section 7 This occurs with RoboGuice 1.1.2 (Guice 2) and RoboGuice 2.0b3 (Guice 3). In Googling around, I found this previous question on Stack Overflow which seemed to be a configuration error, but I don't think that's the problem I'm experiencing... help!

Android dependency-injection roboguice dx link|improve this question asked Feb 28 at 17:16trombonehero33.

It turns out that this problem is related to Dalvik's hard 64k method limit; I have filed a new bug report asking the Android team to fix the poor diagnostic output.

You can rewrite dx code, let it support extended opcode. I hope my answer can help you.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.