-
Notifications
You must be signed in to change notification settings - Fork 378
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
autofill notification disappears #19
Comments
can you create a logcat of this please? |
logcat for KP2AAF: https://gist.github.com/jeroen7s/913e01e0463cdfdf587df9335a76073d |
Thanks for the log! I don't really understand why these events pop up, but it's interesting that the root element's package name actually is com.android.systemui (can be seen from the URL=..):
However, this seems to be different from the swiftkey events. From the logcat I don't see that these should cancel the notification: [ 10-03 10:22:10.156 2949: 2949 D/KP2AAF ] OnAccEvent This means that the event is not discarded as a notification drawer event (which is correct), but it also neither cancels the notification (there is no Cancel Notif) nor does it update it in any way, so that looks ok. Maybe you can create a shorter log with only few accessibility events, focusing on the swiftkey issue? |
@jeroen7s can you please check wtih the 1.02-pre4 which I uploaded to beta channel yesterday? |
it does seem like the notification stays now, thanks a lot, i think the swiftkey issue must have been related, since that's also resolved (opening keyboard adds a notification to the notification tray, that's there to switch to different keyboards, that may have triggered the issue) |
….systemui), also detect launcher from root.getPackageName(), see #19 support for Samsung Browser
when i type a key on my keyboard (swiftkey in my example), regardless of key, including backspace and then slide down the notification tray with the autfill notification, it disappears, untill i leave the app and then open it again, then the autofill notification appears again
The text was updated successfully, but these errors were encountered: