The same problem occurs with the MessageBox in the List example, if I package that unchanged and run the apk or production build on Android 4.0.3.
The first MessageBox comes up as expected, I can press the buttons and read the value. Directly after the first MessageBox animates out, the same MessageBox animates in again and stays on screen, but now I cannot press the buttons. I can tap outside the second MessageBox to escape (if a container exists).
What I noticed in Android 2.2.2:
Sencha Touch runs much faster and is more responsive
no problem with Ext.MessageBox
Ext.browser.getPreferredTranslationMethod() returns 'cssposition' (on Android 4.0.3: 'csstransform')
I wonder if these three are related?
To test this, how can I force Sencha Touch in Android 4.0.3 to render like it does on Android 2.2.2?