TL;DR
Google Play Console forces to show Permissions Declaration Form (see below) as soon as "Create Release" button clicked even if updated APK uploaded without READ_CALL_LOG which caused the warning email from Google before.
Question
How to avoid the Permissions Declaration Form which looks irrelevant if releasing updated APK without sensitive permissions?
Problem in details
PRODUCTION and ALPHA releases were submitted with READ_CALL_LOG permission before Google emailed about prohibit to use it.
Now, during creating new release and once clicking "Create release" button -- it disappears in favor to "Edit release" button, however, there is no release behind (e.g. in BETA track). The only message "You have a release in production/beta/alpha that hasn't been rolled out" within the respective track section is showing.
There is also warning in App Release menu item "You can't edit this app until you create a new app release declaring sensitive permissions.". So, it would be nice to create release which doesn't use sensitive permissions at all.
Could you please advice.
Not appropriate Permissions Declaration Form
Permissions Declaration Form
See Question&Answers more detail:
os 与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…