Assigned
Status Update
Comments
vi...@google.com <vi...@google.com> #2
Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:
Can you confirm if this issue is reproducible on a Pixel/Nexus device?
Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:
Alternate method
Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.
Note: Please upload the bug report and screenshot to google drive and share the folder to
lb...@gmail.com <lb...@gmail.com> #3
@2
- "Can you confirm if this issue is reproducible on a Pixel/Nexus device?"
As I wrote, it's only on Crashlytics, and only "for a single user once, on Android 8, on "Moto E (5)"".
I don't even know when it can occur.
- "Android bug report (to be captured after reproducing the issue)"
How do I get a bug report of users when it was reported on Crashlytics?
Please read what I wrote.
You need to check on the code of the android-x library to see how it could happen, and also check your own logs from users on your own apps.
- "Can you confirm if this issue is reproducible on a Pixel/Nexus device?"
As I wrote, it's only on Crashlytics, and only "for a single user once, on Android 8, on "Moto E (5)"".
I don't even know when it can occur.
- "Android bug report (to be captured after reproducing the issue)"
How do I get a bug report of users when it was reported on Crashlytics?
Please read what I wrote.
You need to check on the code of the android-x library to see how it could happen, and also check your own logs from users on your own apps.
Description
- Steps to reproduce the problem (including sample code if appropriate).
No idea. I just have an app that has DrawerLayout.
The app version is quite new, so I think it's this that is relevant:
implementation 'com.google.android.material:material:1.8.0-alpha01'
- What happened.
It crashed for a single user once, on Android 8, on "Moto E (5)":
Fatal Exception: java.lang.IllegalArgumentException: pointerIndex out of range
at android.view.MotionEvent.nativeGetAxisValue(MotionEvent.java)
at android.view.MotionEvent.getX(MotionEvent.java:2201)
at androidx.customview.widget.ViewDragHelper.processTouchEvent(ViewDragHelper.java:1195)
at androidx.drawerlayout.widget.DrawerLayout.onTouchEvent(DrawerLayout.java:1619)
at android.view.View.dispatchTouchEvent(View.java:11724)
at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2958)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2636)
at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2964)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2650)
at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2964)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2650)
at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2964)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2650)
at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2964)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2650)
at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:2964)
at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2650)
at com.android.internal.policy.DecorView.superDispatchTouchEvent(DecorView.java:445)
at com.android.internal.policy.PhoneWindow.superDispatchTouchEvent(PhoneWindow.java:1828)
at android.app.Activity.dispatchTouchEvent(Activity.java:3297)
at androidx.appcompat.view.WindowCallbackWrapper.dispatchTouchEvent(WindowCallbackWrapper.java:70)
at com.android.internal.policy.DecorView.dispatchTouchEvent(DecorView.java:407)
at android.view.View.dispatchPointerEvent(View.java:11963)
at android.view.ViewRootImpl$ViewPostImeInputStage.processPointerEvent(ViewRootImpl.java:4810)
at android.view.ViewRootImpl$ViewPostImeInputStage.onProcess(ViewRootImpl.java:4624)
at android.view.ViewRootImpl$InputStage.deliver(ViewRootImpl.java:4162)
at android.view.ViewRootImpl$InputStage.onDeliverToNext(ViewRootImpl.java:4215)
at android.view.ViewRootImpl$InputStage.forward(ViewRootImpl.java:4181)
at android.view.ViewRootImpl$AsyncInputStage.forward(ViewRootImpl.java:4308)
at android.view.ViewRootImpl$InputStage.apply(ViewRootImpl.java:4189)
at android.view.ViewRootImpl$AsyncInputStage.apply(ViewRootImpl.java:4365)
at android.view.ViewRootImpl$InputStage.deliver(ViewRootImpl.java:4162)
at android.view.ViewRootImpl$InputStage.onDeliverToNext(ViewRootImpl.java:4215)
at android.view.ViewRootImpl$InputStage.forward(ViewRootImpl.java:4181)
at android.view.ViewRootImpl$InputStage.apply(ViewRootImpl.java:4189)
at android.view.ViewRootImpl$InputStage.deliver(ViewRootImpl.java:4162)
at android.view.ViewRootImpl.deliverInputEvent(ViewRootImpl.java:6736)
at android.view.ViewRootImpl.doProcessInputEvents(ViewRootImpl.java:6675)
at android.view.ViewRootImpl.enqueueInputEvent(ViewRootImpl.java:6636)
at android.view.ViewRootImpl$WindowInputEventReceiver.onInputEvent(ViewRootImpl.java:6839)
at android.view.InputEventReceiver.dispatchInputEvent(InputEventReceiver.java:192)
at android.os.MessageQueue.nativePollOnce(MessageQueue.java)
at android.os.MessageQueue.next(MessageQueue.java:325)
at android.os.Looper.loop(Looper.java:142)
at android.app.ActivityThread.main(ActivityThread.java:6694)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:240)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:769)
- What you think the correct behavior should be.
Shouldn't.
- Is this a security related issue? Yes/No
No.
Link: