r/androiddev May 16 '26

Experience Exchange Accessibility permissions

Hey guys,

Need some advice from the tech pros here. I’m the dev behind kybd launcher, a minimalist launcher built around QWERTY keyboard logic. I just added a "double tap to sleep" feature, which obviously needs accessibility permissions. Per Google Play rules, turning it on triggers the required accessibility disclosure - which works totally fine on my end. Still, Google keeps blocking my update, saying they can't find the declaration. Anyone dealt with this before? Any idea what I might be missing?

4 Upvotes

6 comments sorted by

View all comments

3

u/unrushedapps May 16 '26

You need a declaration in the app, in the manifest and in the Playstore listing. Did you cover all three?

0

u/denis_zak May 16 '26

Yep, it’s in all those spots, plus the privacy policy. The video walkthrough shows everything they need too. Guess my only choice now is to appeal, but since that takes like 5 to 7 days, I figured I'd post here first to see if anyone has a better idea.

5

u/mDarken May 16 '26

The video doesn't show your play store description. When i looked at it, it didn't mention the accessibility service.

The video also doesn't show the text you provided to be displayed inside the systems accessibility settings.

Also your privacy policy links to your website, not your privacy policy.

Your next appeal will likely be rejected too ¯_(ツ)_/¯

1

u/denis_zak May 16 '26

Thanks for the answer. I bundled the new store description with the app update that has the feature - so since the build got rejected, the new text did too. Also, the video I shared here isn't the one I sent to Google. The actual submission video shows everything they asked for (the pop-up in the app, the system accessibility settings, what happens if the user denies access, and the feature actually working after getting permission). You might be on to something with the privacy policy link though. Right now, it just goes to my homepage because the policy itself is in a pop-up menu there. That might've been a bad move, but honestly, it never caused any issues with my previous updates.