Android Question Violation of Permissions policy

dibesw · Mar 14, 2019

I have this runtime permission:

B4X:

in Activity...
rp.CheckAndRequest(rp.PERMISSION_SEND_SMS)


Sub Activity_PermissionResult (Permission As String, Result As Boolean)
    If Permission = rp.PERMISSION_SEND_SMS Then
        If Result = True Then
           'do something
        Else
            ToastMessageShow("Non puoi utilizzare il programma", True)
            Activity.finish
        End If
        rp.CheckAndRequest(rp.PERMISSION_CALL_PHONE)
    End If
    If Permission = rp.PERMISSION_CALL_PHONE Then
        If Result = True Then
           'do something
        Else
            ToastMessageShow("Non puoi utilizzare il programma", True)
            Activity.finish
        End If
    End If
End Sub

Manifest:

B4X:

AddPermission(android.permission.SEND_SMS)
AddPermission(android.permission.WRITE_SMS)

The app works well in my phone
I have B4A v6.31
<uses-sdk android:minSdkVersion="11" android:targetSdkVersion="26"/>

but when i trying upload to google store give me this error message:
I don't understand what I have to do
Thanks!

BillMeyer · Mar 14, 2019

All Here:
https://www.b4x.com/android/forum/t...ssions-are-no-longer-available.98100/#content

Also request that this post be moved to the "Questions" Forum

JohnC · Mar 14, 2019

What this sounds like is that you declared your app as a new SMS "default" app that is intended to REPLACE the users SMS app for ALL SMS functions.

But is seems like Google determined that your app is not a full blown SMS app that supports ALL the major features of an SMS app like send, receive, allow users to add attachments, list conversation threads, etc.

So, if you app was not designed to be a complete replacement of the user's SMS app (a full-function SMS app), then google no longer allows apps to send SMS messages unless it is the users "MAIN" sms app and supports all the expected functionality of a full SMS app.

dibesw · Mar 14, 2019

JohnCody said:
What this sounds like is that you declared your app as a new SMS "default" app that is intended to REPLACE the users SMS app for ALL SMS functions.

But is seems like Google determined that your app is not a full blown SMS app that supports ALL the major features of an SMS app like send, receive, allow users to add attachments, list conversation threads, etc.

So, if you app was not designed to be a complete replacement of the user's SMS app (a full-function SMS app), then google no longer allows apps to send SMS messages unless it is the users "MAIN" sms app and supports all the expected functionality of a full SMS app.

not my app does not want to replace the phone sms app; I just have to be able to send text messages and that's it

JohnC · Mar 14, 2019

dibesw said:
not my app does not want to replace the phone sms app; I just have to be able to send text messages and that's it

That's the problem. Google no longer allows apps to "just send an sms" unless your app is the users "default" SMS app (which would then need to also support receiving sms messages, list conversations, etc.)

Beja · Mar 14, 2019

I believe your app asked the user for permissions more than it's functionality needs.

dibesw · Mar 15, 2019

I read this https://www.b4x.com/android/forum/t...ssions-are-no-longer-available.98100/#content
but I would not use "intent"

is there a way to ask the user to leave the "default" sms manager?

techknight · Mar 15, 2019

again. it is not the user, or the device here.

IT IS GOOGLE! and their policy of not allowing apps to do any of this. It doesn't matter how well you polish that drug or change the look of that drug, boarder protection will not allow that drug to pass!

JohnC · Mar 15, 2019

dibesw said:
I read this https://www.b4x.com/android/forum/t...ssions-are-no-longer-available.98100/#content
but I would not use "intent"

is there a way to ask the user to leave the "default" sms manager?

Actually, if you do not want to make your app a complete SMS app, then sending an SMS message using an Intent might be your only solution to send an SMS message. (Yes, this method is not the cleanest solution because the user would have to click "SEND" in their SMS program before the SMS will actually be sent.)

Martin Larsen · Mar 29, 2019

It does actually not have to be a default SMS app. You can apply for a permit in certain case. Such as an safety & emergency app where the phone needs to send an emergency SMS to a friend or relative. I got such a permission recently:

Hi Developer,

Thanks for contacting the Google Play team.

Status of app: Your app MaydayApp (dk.maydayapp.coverage) Not available on Google Play, pending your action

I’m happy to inform you that we’ve accepted your appeal. I’ve included details below about what additional steps you’ll need to take to get your app to appear on Google Play.

Action required: Submit your app

In order to show your app on Google Play, please submit your app again:

Sign in to your Play Console.

Select your app.

Select Store presence > Store listing.

Click Submit update or Resubmit app.

If the submit button is grayed out, you can make a minor change to your store listing to activate the button. For example, add a space after your app title and then delete it. Once the button turns blue, you can submit your update.

If your app does not request SMS/Call Log permissions, you do not need to resubmit the declaration form.

When I tried to resubmit the app it still complained about the permission though, probably due to Google forgetting to set a flag or something.

For other reason I had to abandon the app so I didn't go any further with it.

I just post this to encourage people to make an appeal if they feel the SMS feature is an important core function.

Android Question Violation of Permissions policy

dibesw

Active Member

BillMeyer

Well-Known Member

JohnC

Expert

dibesw

Active Member

JohnC

Expert

Beja

Expert

dibesw

Active Member

techknight

Well-Known Member

JohnC

Expert

Martin Larsen

Active Member

Similar Threads

Android Question Violation of Permissions policy

Active Member

Well-Known Member

Expert

Active Member

Expert

Expert

Active Member

Well-Known Member

Expert

Active Member

Similar Threads

Privacy & Transparency

Privacy & Transparency