android - Removed permissions still show up in Play Store -
i pushed beta version google play accidentally added more permissions compared version that's current in production.
before pushing final new version production via staged rollout, removed permissions, despite that, users still complaining new permissions when received update on play store.
why new permissions still visible? removed apk beta channel, neither of production apks (both old one, , new 1 in staged rollout) have new permissions. see new permissions in play store listing.
by using newer sdk not changing targetsdkversion of imported modules, automatically inherited implicit permissions.
for one, there 1 library targetsdkversion of 3 - automatically add read_phone_state, documented in this answer, , the official docs.
this can seen looking @ manifest merger log in build/output/logs/manifest-merger-release-report.txt:
android:uses-permission#android.permission.read_phone_state implied androidmanifest.xml:2:1 reason: com.foo.library has targetsdkversion < 4
the other problem having read_contacts set, @ least 1 library used both minsdkversion , targetsdkversion < 15. automatically added read_call_log. see the documentation this. curiously enough didn't see mention of in merger log, may have missed it.
the final apk permissions can checked aapt:
aapt dump badging build\outputs\apk\foo-release.apk
that prints out list of permissions.
full credit commonsware leading me this. mark!
Comments
Post a Comment