Welcome to OGeek Q&A Community for programmer and developer-Open, Learning and Share
Welcome To Ask or Share your Answers For Others

Categories

0 votes
1.2k views
in Technique[技术] by (71.8m points)

android - How to correctly fill the permission declaration form in the google play console?

I have one application which used to be taking sensitive SMS permissions. But I removed them and tried to upload a new APK without those permissions. But when submitting the app we are required to choose at least one of the options from the list. But am clear that we do not have to choose any of the below options. Is there any ways to override the permission declaration form as I'm not able to find the option "I don't use any of the options above".

Here is the list of permissions. If anyone knows the correct choice for this type of app I’d appreciate the advice.

==== Permissions Choices =======

Default SMS handler

Default Phone handler

Default Assistant handler

Transactional backup and restore for users and archive for enterprise (time-limited/non-continuous)

Enterprise SMS call archives

Caller ID, spam detection, and blocking

Connected device companion apps (for example, smartwatch or automotive)

Cross-device synchronization or transfer of SMS or calls

SMS-based financial transactions and related activity where access is restricted to financial SMS transactions (for example, 5-digit messages)

SMS based money management

Proxy calls

Services - Carrier

Services - OEM

Device Automation

Physical safety / emergency alert apps (e.g., senior safety)

Call-based OTP account verification

Using SMS_CB_RECEIVED for customer communications (e.g., Smart Zone Cast service)

Write and Show Call History in Dialer

See Question&Answers more detail:os

与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…
Welcome To Ask or Share your Answers For Others

1 Reply

0 votes
by (71.8m points)

After Mar 9, 2019, The option of No, this release does not meet the SMS and call log permissions policy has been gone, and we stuck in the Declaration form that not exactly needed after we removed the sensitive permission list.

I solved that issue by the following steps:

All our work will be in "App releases" tab enter image description here

  1. Make sure you don't use any of the sensitive permissions for the last APK that you uploaded in the Google Console play You can check the final list of permissions by open production track or any track that has the last APK and open the required permissions:

    • click on the android app bundle
    • expand the "Required permissions" enter image description here

    • If all your APK permissions not on the list of the google sensitive permissions high risk or sensitive permissions you ready to go to the next step

  2. Remove all Active APKs that using the sensitive permissions from all Release tracks.

Now check all Tracks (Open track, Closed tracks, Internal test track & Pre-registration)

  • Click on Manage for every track that has an Active sensitive permissions APK
  • Create Release
  • DON'T choose any active APK just make sure your Active sensitive permissions APK in the Retain section to be deactivated

enter image description here

  • Choose any option from Declaration form and click review rollout
  • Do the above steps with all active tracks that have active APK with sensitive APK except the Production Track.

Then for the Production track Create Release with your Latest APK (without sensitive APK) and you will find that Declaration form has gone.

Submit and Rollout


与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…
OGeek|极客中国-欢迎来到极客的世界,一个免费开放的程序员编程交流平台!开放,进步,分享!让技术改变生活,让极客改变未来! Welcome to OGeek Q&A Community for programmer and developer-Open, Learning and Share
Click Here to Ask a Question

...