Databases
StackOverflow2013
Postsdbo
POMockito and DexLibs with Android on "real device" fails with ExceptionInitializer
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POMockito and DexLibs with Android on "real device" fails with ExceptionInitializer
    primarykey
    data
    text
    <p>just wanted to clarify my understanding of the error I get is correct please...</p> <pre><code>java.lang.ExceptionInInitializerError at org.mockito.internal.creation.jmock.ClassImposterizer.createProxyClass(ClassImposterizer.java:85) at org.mockito.internal.creation.jmock.ClassImposterizer.imposterise(ClassImposterizer.java:62) at org.mockito.internal.creation.jmock.ClassImposterizer.imposterise(ClassImposterizer.java:56) at org.mockito.internal.creation.CglibMockMaker.createMock(CglibMockMaker.java:23) at org.mockito.internal.util.MockUtil.createMock(MockUtil.java:26) at org.mockito.internal.MockitoCore.mock(MockitoCore.java:51) at org.mockito.Mockito.mock(Mockito.java:1243) at org.mockito.Mockito.mock(Mockito.java:1120) at uk.co.flurrished.test.ResultActivityTest.setUp(ResultActivityTest.java:51) at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:169) at android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:154) at android.test.InstrumentationTestRunner.onStart(InstrumentationTestRunner.java:529) at android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:1448) Caused by: java.lang.VerifyError: org.mockito.cglib.core.ReflectUtils at org.mockito.cglib.core.KeyFactory$Generator.generateClass(KeyFactory.java:167) at org.mockito.cglib.core.DefaultGeneratorStrategy.generate(DefaultGeneratorStrategy.java:25) </code></pre> <p>As you can see, this is littered with cglib references, and not a mention of dexedlibs. Is it safe to assume that the dexing isn't happening and Mockito is trying to use CGLib to construct the Reflection bootstrapping. If so, given I have mockito-1.9.5-all and both the dexmaker and dexmaker-mockito in my libs, does anyone know how I can force it to use these dex libs. Stackoverflow and Googlecode is littered with this issue, but nothing works for me yet. TDD on Android seems all but impossible at the moment.</p> <p>Many thanks</p> <p>Mike</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USBrice
    1. USMikeB
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COAlso, just compiled Mockito 1.9.8 to see if different, but is same error.
      singulars
      1. POMockito and DexLibs with Android on "real device" fails with ExceptionInitializer
      1. USMikeB
    2. COHum this should work, you definitely should check the classpath when the test is run on Dalvik
      singulars
      1. POMockito and DexLibs with Android on "real device" fails with ExceptionInitializer
      1. USBrice
    3. COThanks Brice. No luck. Do you know whether I should be seeing cglib in the stacktrace at all or is this normal - I don't know what I'm looking for in terms of clues as to the dexedLibs being loaded? They are in my bin folder, I can see them, and my .classpath lists them
      singulars
      1. POMockito and DexLibs with Android on "real device" fails with ExceptionInitializer
      1. USMikeB
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload