On Jun 26, 12:55 am, bazookier <[email protected]> wrote: > I have two classes declared in one package. > One accesses the other. > Made a dex file contain this whole package. > When running, it reported the following error: > > Class resolved by unexpected DEX: ...... > ......
The message means it expected the class to be resolved from one DEX, but it actually came from another; i.e. you have two copies of the same class available to the app. The "dexopt" optimizations assume that, if class A refers to class B in the same DEX file, that it will come from there when the app runs. If the class loader pulls class B from somewhere else, the optimizations are invalid and could cause the VM to crash. So it refuses to load class B. --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
