Android 3.1 Crash - pointerIndex out of range

Solar2D Android
#1

On a Honeycomb 3.1 tablet I’m seeing crashes with multitouch. The same issue is not occurring on smartphones. Has anyone else experienced this? It seems to be directly related to system.activate( ‘multitouch’ ); If I remove the multitouch call the crash no longer occurs.

D/AndroidRuntime(13229): Shutting down VM W/dalvikvm(13229): threadid=1: thread exiting with uncaught exception (group=0x401ae760) E/AndroidRuntime(13229): FATAL EXCEPTION: main E/AndroidRuntime(13229): java.lang.IllegalArgumentException: pointerIndex out of range E/AndroidRuntime(13229): at android.view.MotionEvent.nativeGetAxisValue(Native Method) E/AndroidRuntime(13229): at android.view.MotionEvent.getX(MotionEvent.java:1549) E/AndroidRuntime(13229): at com.ansca.corona.version.android8.AndroidVersionSpecific.motionEventGetX(AndroidVersionSpecific.java:68) E/AndroidRuntime(13229): at com.ansca.corona.CoronaActivity.onTouchEvent(CoronaActivity.java:337) E/AndroidRuntime(13229): at android.app.Activity.dispatchTouchEvent(Activity.java:2312) E/AndroidRuntime(13229): at com.android.internal.policy.impl.PhoneWindow$DecorView.dispatchTouchEvent(PhoneWindow.java:1701) E/AndroidRuntime(13229): at android.view.View.dispatchPointerEvent(View.java:4677) E/AndroidRuntime(13229): at android.view.ViewRoot.deliverPointerEvent(ViewRoot.java:2348) E/AndroidRuntime(13229): at android.view.ViewRoot.handleMessage(ViewRoot.java:2017) E/AndroidRuntime(13229): at android.os.Handler.dispatchMessage(Handler.java:99) E/AndroidRuntime(13229): at android.os.Looper.loop(Looper.java:132) E/AndroidRuntime(13229): at android.app.ActivityThread.main(ActivityThread.java:4025) E/AndroidRuntime(13229): at java.lang.reflect.Method.invokeNative(Native Method) E/AndroidRuntime(13229): at java.lang.reflect.Method.invoke(Method.java:491) E/AndroidRuntime(13229): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:841) E/AndroidRuntime(13229): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:599) E/AndroidRuntime(13229): at dalvik.system.NativeStart.main(Native Method) W/ActivityManager( 126): Force finishing activity com.beatgang.harp/com.ansca.corona.CoronaActivity [import]uid: 4596 topic_id: 14225 reply_id: 314225[/import]

#2

If I remove all touch event listeners, the error still occurs. Removing the call to active system.multitouch is the only way to avoid having the corona app crash.

--system.activate( "multitouch" ) [import]uid: 4596 topic_id: 14225 reply_id: 52428[/import]

#3

can you enter a bug, some code to go with this crash and let me know bug number

thanks

.c
[import]uid: 24 topic_id: 14225 reply_id: 52541[/import]

#4

Case 7701

All that is necessary to replicate the crash is, system.activate( 'multitouch' ), run the app on an Android 3.1 tablet, and touch with three fingers. I’ve gotten 37 error reports from the android market this week. [import]uid: 4596 topic_id: 14225 reply_id: 52579[/import]

#5

I’m getting more & more emails about this. Android 3.1 must be spreading. Reports from Iconia, Eee Pad, Xoom, and Galaxy devices. [import]uid: 4596 topic_id: 14225 reply_id: 53456[/import]

#6

Can you please increase the priority of Honeycomb support? There are quite a few 3.1 devices on the market now, we’re getting error reports on the market, and even emails/comments regarding multitouch crashes.

Thanks. [import]uid: 4596 topic_id: 14225 reply_id: 54082[/import]

#7

I’m getting some users requesting refunds based on the multitouch crashes on 3.1 tablets. [import]uid: 4596 topic_id: 14225 reply_id: 54117[/import]

#8

Same problem here. Even if you won’t support honeycomb, this is a bad issue and should be simple to fix.

At the very least, the app should at least always disable multitouch if it’s running on honeycomb. [import]uid: 78970 topic_id: 14225 reply_id: 54249[/import]

#9

Getting some 1 star ratings based on this issue now. Is there a way to prevent Corona apps from being installed on Honeycomb tablets at this time? [import]uid: 4596 topic_id: 14225 reply_id: 55586[/import]

#10

What corona build are you guys using?

Can you isolate the code and send?

I have not received any emails from anyone complaining about honeycomb.

Am not saying that there is not an issue, but need to know if you can isolate so we can debug here.

Carlos [import]uid: 24 topic_id: 14225 reply_id: 55588[/import]

#11

I submitted a bug report on Aug 24th, case #7701. I’m able to reproduce the crash by using 3 or more fingers on Honeycomb Tablets when multitouch is enabled.

All that is required is to publish an apk with multitouch enabled, and then to touch the screen with 3 or more fingers. That’s it. [import]uid: 4596 topic_id: 14225 reply_id: 55590[/import]

#12

k [import]uid: 24 topic_id: 14225 reply_id: 55592[/import]

#13

I’ve experienced this for awhile now, through a series of daily builds. I’m currently on 617. [import]uid: 4596 topic_id: 14225 reply_id: 55596[/import]

#14

I was able to reproduce the problem on a Motorola Zoom (os 3.2) and the MultitouchFingers sample app. Four fingers causes the app to crash. Sent to Engineering for a fix. [import]uid: 7559 topic_id: 14225 reply_id: 55601[/import]

#15

We have Iconia Tabs running Android 3.1. They crash everytime with 3 fingers, almost immediately. It sounds like Android 3.3 will bring the number of supported fingers up to 5 ; )

Thanks Tom!
[import]uid: 4596 topic_id: 14225 reply_id: 55602[/import]

#16

Engineering fixed the problem. It will be in the next daily build. [import]uid: 7559 topic_id: 14225 reply_id: 55619[/import]

#17

@Carlos @Tom @Engineering

Thank you very much. [import]uid: 4596 topic_id: 14225 reply_id: 55637[/import]