Infeasible
Status Update
No update yet.
Comments
am...@google.com
Thank you for the report.
Can you please provide the below details if possible?
At least, provide Device build details -- Device Make, Model, Android OS Version
Please provide a sample project and apk to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given sample project or apk.
Frequency
How frequently does this issue occur? (e.g 100% of the time, 10% of the time)
Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:https://developer.android.com/studio/debug/bug-report#bugreportdevice
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 files to google drive and share the folder to android-bugreport@google.com, then share the link here.
Can you please provide the below details if possible?
At least, provide Device build details -- Device Make, Model, Android OS Version
Please provide a sample project and apk to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given sample project or apk.
Frequency
How frequently does this issue occur? (e.g 100% of the time, 10% of the time)
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 files to google drive and share the folder to android-bugreport@google.com, then share the link here.
lb...@gmail.com
@2 Read what I wrote. and watch the video.
It shows you everything.
Here:
moto e6s
Android 9
It shows you everything.
Here:
moto e6s
Android 9
am...@google.com
Thanks for the report. The development team is looking into this issue.
am...@google.com
It looks like the issue happens only on Motorola, Android 9. We won't be able to do anything about this. So, please contact respective OEM for such issues.
lb...@gmail.com
@5 Actually I got it now on "Samsung Galaxy Note10+" with Android 11:
https://console.firebase.google.com/u/0/project/app-manager-cdf2c/crashlytics/app/android:com.lb.app_manager/issues/cb499e301d18b47e13947b9085c8ca98?time=last-seven-days&sessionEventKey=607EC30F001F00010FC9C9E258791A45_1532043101110865610
And I'm pretty sure I saw it on more cases too.
Why am I supposed to be the one to contact the OEMs when Google is the one that's supposed to set the rules for them?
And I'm pretty sure I saw it on more cases too.
Why am I supposed to be the one to contact the OEMs when Google is the one that's supposed to set the rules for them?
Description
- Steps to reproduce the problem (including sample code if appropriate).
Not sure, but according to the logs, it's just long pressing or dragging of TextView/EditText.
- What happened.
Crash
- What you think the correct behavior should be.
Shouldn't.
The logs :
Fatal Exception: java.lang.IllegalStateException: Drag shadow dimensions must be positive
at android.view.View.startDragAndDrop(View.java:24232)
at android.widget.Editor.startDragAndDrop(Editor.java:1165)
at android.widget.Editor.performLongClick(Editor.java:1191)
at android.widget.TextView.performLongClick(TextView.java:11393)
at android.view.View.performLongClick(View.java:6659)
at android.view.View$CheckForLongPress.run(View.java:26059)
at android.os.Handler.handleCallback(Handler.java:873)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:193)
at android.app.ActivityThread.main(ActivityThread.java:6704)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:916)