IssueTracker

We have passed this defect on to the development team and will update this issue with more information as it becomes available.

Any news on this issue?

Hello,

Is there any update on the issue?

Thanks

I am facing the same issue with my app - any update or workaround on this? Thanks!

I had the same issue , please fix it!

I am also facing same issue. Please update.

Our engineering team has fixed this issue. It will be available in a future Android release.

Has it been released? In what version? If we experience this issue, what should we do to ensure that we are not using an old version?

hi, i am facing the same bug on a Google Pixel with android 11, was the bug realy fixed?

Fixed and released are two very different things :(

does anyone found the solution?

Dear Google Team! Could you share the current status of this problem?

In which version it had been fixed?
Have you any documentation about fix and new behavior?
How we can test the fix?

Have you faced this problem in the last Android release?
Could you recommend a workaround?

I am also facing same issue. Please let me know if any solutions for above issue.
Thank you.

Google,

Status marked as "Fixed" but when will it be released ? Facing the same issue.

Thanks

Same here, why don't fix? I can't use some installed apps.

google wtf wake tf up

How can a little bug fix last more than 6 years ??? If you can no longer maintain Android, put it back fully Open Source and we will fix it by ourselves. This is hilarious and frustrating !!!!

Hello, the service is stopped automatically even no crash from my app, and also no accessibility event.

Dear Google Team! Could you share the current status of this problem?

In which version it had been fixed?
Have you any documentation about fix and new behavior?
How we can test the fix?

Have you faced this problem in the last Android release?
Could you recommend a workaround?

This still hasn't been addressed even now in June 2023, Completely unacceptable.

seems that running AccessibilityService in separate process could be as a workaround

what the hell ? still no fix ?

Title: Android Accessibility Service Malfunctioning After App Upgrade, Requires Programmatic Fix

Question:
I'm encountering an issue with the Accessibility Service in my Android app after users upgrade from an older version to a newer version.

The problem manifests after the app upgrade, where the Accessibility Service seems to malfunction, and users are presented with error messages like "This app isn't working correctly. Turn it off above, then turn it on again, to restart it" on Samsung Tab A7 Lite and "This service is malfunctioning" on Micromax devices.

Restarting the device or manually restarting the Accessibility Service temporarily resolves the issue. However, as a developer, I'm seeking a programmatic solution to address this problem automatically, as restarting the service or the device should not be the expected behavior after an app update.

I've tried examining the update logic, but I couldn't find any specific issues related to the Accessibility Service in the codebase. I'm wondering if there are any additional steps I can take during the app upgrade to ensure the Accessibility Service works seamlessly without requiring manual intervention.

Is there a way to programmatically fix the Accessibility Service after an app update? Are there any specific considerations, best practices, or compatibility checks that I should incorporate into my codebase to prevent this issue from occurring in the future?

Any insights or guidance on resolving this matter programmatically would be greatly appreciated. Thank you!

I recently noticed following fix made by Google on 2019:
https://cs.android.com/android/_/android/platform/frameworks/base/+/fbac83822e8598a9d89118ef9dc48733443d64ea

"After an accessibility service crashes a few times in a short period of time, framework would add it into a “blacklist”. User wouldn’t be able to use (re-enable) it. If users express an intent in them working again, we remove the crashed accessibility service from the blacklist."

I'm not 100% sure but this situation "crashes a few times in a short period of time" may occur when that app gets version up since
system try to stop the app first for version up.
This fix was added on 2019 October, so I guess Android 11+ has this fix.

NOTE:
Probably thanks to above fix, in recent Android 11+ devices, I seldom see the issue like Accessibility service stop working after app crash or version up.
However even in latest Android 11+,  accessibility service stops from time to time, reported by users of my app...
(Device power saving feature may be related in some case but root cause is still unclear.)

I am using Android 13. Still I am facing same problem in one of my device (Lava Blaze 2). I have tried many different ways but no luck. The accessibility service is not working after some time. Please fix thi issue.

I am also still facing the issue for my devices. After some time my foreground service is killed by OS and even if it is restarted it can't recover accessibility service and get a mulfunctioning error.
- OnePlus 7T Pro - Android 12
- Crosscall Xcore 5 - Android 11