I uploaded a new version of the app to the Google Play Console, but the following error appeared twice in a row.

Not declared in the Play Console version. android.permission.BIND_ACCESSIBILITY_SERVICE Authority is included.

The new ABB. isAccessibilityTool=true When I checked the combined manifesto, there was only one accessibility service. Initially, I suspected that it was a build problem or that the permission settings were wrongly touched.

Seeking the cause.

Play Console doesn’t only scan newly uploaded AABs, but it’s too late to find out that it scans up to previous builds of an activated internal test, a private test track.

As a matter of fact, the next version was still active.

• Private Test: Version Code xx
• Internal testing: version code x

The past of these two. isAccessibilityTool=true Play Console continued to judge the entire app as an accessibility tool based on this value, resulting in the same authorization errors corresponding to two previous versions, each one, and a total of two.

The solved way.

First, we stopped the internal testing and private test tracks that we no longer use, and then the Play Console accessibility declaration screen changed to normal.

When you save the accessibility declaration in this state, both errors disappear at the same time. 출시 준비됨Since then, a new version of the code has been submitted to Google review together with the production release and a private test track suspension proposal.

and clean.

If the same sensitive permission error is repeated on the Play Console, you do not need to re-create AAB immediately.

1. Combined Manifesto of the New AAB
2. App Bundle and APK on Play Console
3. Currently active internal, public and private test tracks
4. Rest permissions and isAccessibilityTool settings
5. Accessibility declarations now matching the actual nature of the app

The key to this problem was not the code, but the test build, which was long ago posted and abandoned, continued to create errors without being deleted.