Develop Reference

App rejected on playstore due policy violation default phone handler

I am trying to upload an bundle to play with the following permissions:
<uses-permission android:name="android.permission.CALL_PHONE" />
<uses-permission android:name="android.permission.READ_CONTACTS" />
<uses-permission android:name="android.permission.WRITE_CONTACTS" />
<uses-permission android:name="android.permission.READ_CALL_LOG" />
<uses-permission android:name="android.permission.WRITE_CALL_LOG" />
<uses-permission android:name="android.permission.READ_PROFILE" />
<uses-permission android:name="android.permission.MANAGE_ACCOUNTS" />
<uses-permission android:name="android.permission.GET_ACCOUNTS" />
<uses-permission android:name="android.permission.PROCESS_OUTGOING_CALLS" />
<uses-permission android:name="android.permission.NFC" />
<uses-permission android:name="android.permission.READ_PHONE_STATE" />
My app's core functionality is to work as a complete dialer like other phone apps like google phone, it shows call history, contacts place calls, etc. I have filled the declaration form and also gave reasons why I need the following permissions but still, my app is getting rejected again and again, also filed an appeal for the same still waiting for a response, please can anyone guide me what I am doing wrong.
below is the message sent by Google:-
Issue: Violation of Permissions policy After reviewing your app, we
found that it doesn’t qualify to use the requested permissions for the
following reason(s): Requested permissions do not match the core
functionality of the app You declared the Default Phone handler (and
any other core functionality usage while the default handler) as the
core functionality of your app. However, after review, we found that
your app does not match the declared use case(s). Learn more about
permitted uses and exceptions. Please either:
• Make changes to your app so that it meets the requirements of the
declared core functionality or,
• Select a use case that matches your app’s functionality

Some of requirements may not be met:
Your app must be able to perform the functionality for which it's a default handler. For example, a default SMS handler should be able to send text messages.
Your app must provide a privacy policy.
Your app must make its core functionality clear in the Play Store description. For example, a default Phone handler should describe its phone-related capabilities in the description.
Your app must declare permissions that are appropriate for its use case. For more details about which permissions you can declare as a given handler, see the guidance on using SMS or call log permission groups in the Play Console Help Center.
Your app must ask to become a default handler before it requests the permissions associated with being that handler. For example, an app must request to become the default SMS handler before it requests the READ_SMS permission.

Xamarin Android App Play Console Sensitive Permissions

I installed a new application to release it to the play console. I installed Apk. First, I uploaded it to the open beta channel, but it always seems to be under review.
Later, after installing each apk, I get an e-mail about application permissions, they say that they do not comply with their privacy and sensitivity policies.
These appear in the permissions required by apk on the play console:
android.permission.ACCESS_NETWORK_STATE, android.permission.INTERNET, android.permission.READ_EXTERNAL_STORAGE, android.permission.WAKE_LOCK, android.permission.WRITE_EXTERNAL_STORAGE, com.google.android.c2dm.permission.RECEIVE
This is the content of mail:
Requested permissions do not match core functionality of the app
You declared Select Carrier Services and Device Automation as the core functionality of your app. However, after review, we found that your app does not match the declared use case(s). Learn more about permitted uses and exceptions.
Please either:
Make changes to your app so that it meets the requirements of the declared core functionality or,
Select a use case that matches your app’s functionality
Sensitive permission
Your app does not qualify for use of the requested permissions. Permission requests should make sense to users. You may only request permissions that are necessary to implement critical current features or services in your application. You may not use permissions that give access to user or device data for undisclosed, unimplemented, or disallowed features or purposes.
This is the my AndroidManifest.xml and permissions:
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.WAKE_LOCK" />
<uses-permission android:name="com.google.android.c2dm.permission.RECEIVE" />
If anyone has an idea or can help I would be very glad.
Although I changed it 8 times and installed the apk, I did not get approval for how many days and I constantly receive the mail I sent the content above, every time I send an apk..

Google Play rejected app because of it's uploading users' Contact information

App removed from google play store due to the following reason:
APK HAS A PROMINENT DISCLOSURE BUT THE DISCLOSURE IS NOT ADEQUATE Your app is uploading users' Contact information to
https://domen.com without an adequate disclosure.
Because of application is for international call app we are using a lot of permissions
<uses-permission android:name="android.permission.USE_CREDENTIALS" />
<uses-permission android:name="android.permission.CALL_PHONE" />
<uses-permission android:name="android.permission.WRITE_CONTACTS" />
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
<uses-permission android:name="android.permission.READ_PHONE_STATE" />
<uses-permission android:name="android.permission.READ_CONTACTS" />
<uses-permission android:name="android.permission.VIBRATE" />
<uses-permission android:name="android.permission.INTERNET" />
The application does not upload information about the user's contact ("Address Book").
In a not google mentioned that the Contact data is sent to our host.

I feel your pain; Google Play rejection is often arbitrary and getting to the bottom of it (with an actual human on the other end) is next to impossible. That said, Google Play support is considered off-topic here. This question will probably be closed soon enough.
That said, extra permissions are not the reason. What you probably have is a genuine case of an HTTP request with some information that originates in the contact list. As far as I can tell, Google's screening robot uses some kind of data path analysis internally. Obfuscating the data path (by using reflection and such) might get you off the hook.
One more data point: my app was once delisted over an old version in the beta channel. The beta version from a couple of years ago had a behavior that Google once tolerated but then didn't (a direct link to an APK). Once I've replaced the version in the beta channel, Play was happy again. See if you have something like that. The takedown notice I've got from them didn't make it clear.

The Reason For Rejection after a over 2 months Struggle is cause of Non Compliance of the apps in any of the stages Internal / Closed / Open Testing / Production
Please make sure once the app is Removed by google ,the roll out the release to 100% & Make sure all the Internal / Closed / Open Testing / Production have the version which is complaint with the Google Policy.
with "Google bots" taking over approval process and if u enter this Policy Loop and will never be able to reach the Contacts to find help.

how can I publish an android app with android.permission.READ_CALL_LOG?

I have an android app to analyse data of calls using android.permission.READ_CALL_LOG but I got no way to upload it how can I do this.
<uses-permission android:name="android.permission.READ_CALL_LOG" />
<uses-permission android:name="android.permission.WRITE_CALL_LOG" />

I don't think you can upload an app with those permission and SMS permissions to the store anymore due to an update to the playstore an applications privacy policy . However, there are a few modifications you can make to your code which might allow ou to be able to push the application. Please see the materials below as reference:
https://android-developers.googleblog.com/2019/01/reminder-smscall-log-policy-changes.html
https://proandroiddev.com/no-more-sms-call-log-permissions-now-what-9b8226de7827
https://support.google.com/googleplay/android-developer/answer/9047303

Issue: Violation of Permissions policy After reviewing your app while uploading Android app on Store

While uploading my Android app , I receive a rejected mail from Google says that
Issue: Violation of Permissions policy After reviewing your app, we found that it doesn’t qualify to use the requested permissions for the following reason(s):
Based on our review, we found your app’s expressed user experience did not match your declared core functionality { Default SMS handler (and any other core functionality usage while default handler), Cross-device synchronization or transfer of SMS or calls, SMS-based financial transactions (e.g., 5 digit messages), and related activity including OTP account verification for financial transactions and fraud detection, Track, budget, manage SMS-based financial transactions (e.g., 5 digit messages) and related account verification }. Please remove these permissions from your app.
Your app seems to be a {Violation Monitoring app} and does not meet any of the allowed use cases. Hence, we cannot provide SMS/Call Log permissions.
I tried to search on it and I didn't find a real solution for my problem
Here is my Permissions
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
<uses-permission android:name="android.permission.RECEIVE_SMS" />
<uses-permission android:name="android.permission.READ_SMS" />
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE"
/>
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"
/>
<uses-permission android:name="android.permission.CAMERA" />
<uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION"
/>
<uses-permission android:name="android.permission.ACCESS_GPS" />
<uses-permission android:name="android.permission.ACCESS_ASSISTED_GPS" />
<uses-permission android:name="android.permission.ACCESS_LOCATION" /> ```

My app used read sms permission which allowed my app read otp sms send to user mobile device to verify user mobile number.
So i too received this violation policy permission mail stating i am using read sms permission in my app.Using that permission i was able toread OTP automatically from the sms.
But according to new google guidelines,we cant use read sms permission for above mentioned account verification.So right now i have removed sms read permission and made user to enter the otp received in sms manually.
If you are using read sms permission ,there are certain requirements to be met.
For apps requesting access to the SMS or Call Log permissions, the intended and permitted uses include default SMS handling, default
phone handling, or Assistant handling capability. Apps must be
actively registered as the default SMS, Phone, or Assistant handler
before prompting users to accept any of the above permissions and must
immediately stop the use of the permission when they no longer are the
default handler.
I got information from this link.
https://support.google.com/googleplay/android-developer/answer/9047303
Hope this helps you.