Android Question Google sms permisions changes

[hookshy]

From the letter that I have received I see that I have to limit my app functionality and wonder how I could do this.

Question:
Does this code below needs any permitions ?

    Dim r As Reflector
    r.Target = r.RunStaticMethod("android.telephony.SmsManager", "getDefault", Null, Null)
    Dim parts As Object
    parts = r.RunMethod2("divideMessage", Message, "java.lang.String")
    r.RunMethod4("sendMultipartTextMessage", _
      Array As Object(Destination, Null, parts, Null, Null), _
      Array As String("java.lang.String", "java.lang.String", _
         "java.util.ArrayList", "java.util.ArrayList", "java.util.ArrayList"))

I am very confused about all these changes would I be able to make calls by voice or send sms without adding these permitions ?


Here is a letter from google regarding sms permisions

Hello Google Play Developer,

In October, we announced updates to our Permissions policy that will limit which apps are allowed to request Call Log and SMS permissions. This policy will impact one or more of your apps.

Only an app that has been selected as a user's default app for making calls or text messages, or whose core functionality is approved for one of the exception use cases, will be able to request access to Call Log or SMS permissions.

Action required

Below, we've listed apps from your catalog which do not meet the requirements for permission requests. Please remove any disallowed or unused permissions from your app's manifest (specified below), migrate to an alternative implementation (e.g. SMS Retriever API for most cases of OTP verification), or evaluate if your app qualifies for an exception.

Next steps
Read through the Permissions policy and the Play Console Help Center article, which describes intended uses, exceptions, invalid uses, and alternative implementation options for usage of Call Log or SMS permissions.

Update your app or submit a Permissions Declaration Form.

Option 1) If your app does not require access to Call Log or SMS permissions: Make appropriate changes to your app by removing the specified permissions from your app's manifest or migrating to an available alternative implementation by January 9, 2019.

Option 2) If your app is a default handler or you believe your app qualifies for an exception: Please submit a request via the Permissions Declaration Form. You do not need to have implemented APK changes in order to submit a form. Declaration Forms received by January 9, 2019 may be eligible for additional time to make changes to bring their app(s) into compliance. If you have recently submitted a Permissions Declaration Form, we are in the process of reviewing your information and will respond to your application.

Make sure that your app is otherwise compliant with all other Developer Program Policies to prevent your app from being removed.
Alternatively, you can choose to unpublish the app.

Our Developer Program Policies are designed to provide a safe and secure experience for our users while also giving developers the tools they need to succeed. That is why we will remove apps that violate our policies. In cases of repeated or serious violations of our policies, we may also terminate your developer account and any related developer accounts.

We appreciate your willingness to partner with us as we make these improvements to better protect users.

Affected apps

Affected apps and permissions are listed below, up to 20; if you have additional apps, please ensure that they are also compliant with the Permissions policy.

com.hsw.voice_lite   SEND_SMS, RECEIVE_SMS, READ_SMS, WRITE_SMS, READ_CALL_LOG   
com.hsw.lite_pack   READ_CALL_LOG, READ_SMS, RECEIVE_SMS, WRITE_SMS, SEND_SMS

 

[Computersmith64]

From reading the details in the Developer Policy Center, I don't think what you are trying to do will satisfy the requirements. What they are saying is that your app can't request those permissions unless the user has selected it as the default app for making calls or text messages - so by extension, your app isn't allowed to use that functionality unless the user has made it the default app.

I think what you probably need to do is something like:

* Set up the permissions to be requested via runtime permissions, but don't actually request them.
* When the user starts your app, ask them if they want your app to be the default app for making calls & texts.
* If they agree, request the runtime permissions.
* If they don't agree, don't request the runtime permissions & tell them that the app won't work unless it's the default.
* If at any time they select a different app as the default, you need to disable those permissions (not sure how you do that).

- Colin.

 

[hookshy]

From reading the details in the Developer Policy Center, I don't think what you are trying to do will satisfy the requirements. What they are saying is that your app can't request those permissions unless the user has selected it as the default app for making calls or text messages - so by extension, your app isn't allowed to use that functionality unless the user has made it the default app.

I think what you probably need to do is something like:

* Set up the permissions to be requested via runtime permissions, but don't actually request them.
* When the user starts your app, ask them if they want your app to be the default app for making calls & texts.
* If they agree, request the runtime permissions.
* If they don't agree, don't request the runtime permissions & tell them that the app won't work unless it's the default.
* If at any time they select a different app as the default, you need to disable those permissions (not sure how you do that).

- Colin.

Thanks,
The app will change dramaticaly... I am sure nobody will change their defaut settings a lot of voice command app will be affected