Play Store "RECEIVE_SMS" permissions issue

[TIMAI2]

My guess is that the Texting component adds the RECEIVE_SMS permission by default, no way to undo this with blocks.

As far as I know, the only way around this is to decompile your apk, edit the manifest file to remove the RECEIVE_SMS permission, then recompile the apk and re-sign it. You will need a program like Android Studio or apkTool to do this.

Here is an example:

Build apk whitout internet permission

I checked it with A2M. No problem removing this line <uses-permission android:name="android.permission.INTERNET"/> from the Manifest and build the APK. You will likely need to update the apktool.jar file: https://ibotpeaches.github.io/Apktool/install/ . Otherwise you can use → APK Studio Editor:

[Steven_Rice]

Does everyone agree that this is the only way, or are there any other ideas?

[eAcademy]

show app rejection email sent by review team, your app can be published for sure.

[Steven_Rice]

This email?

[eAcademy]

Do not try to appeal else your account be suspended

[ewpatton]

The RECEIVE_SMS permission is added if the ReceivingEnabled property of any Texting component is set to something other than Off, so you should double check that. If you've used extensions, any one of them could also add the RECEIVE_SMS permission as well. Attached is an example project that will not have the Android SEND/RECEIVE SMS permissions when compiled.

NoReceiveTest.aia (1.6 KB)

[ABG]

(added to FAQ)

FAQ Section: SMS

Error 908: Permission Receive SMS - Taifun Sending an SMS text via the Activity Starter - Joseph Sepielli SMS stopped auto-sending because of Google policy change - TimAI2, Hal@mit How to avoid RECEIVE_SMS permission for Play Store - @ewpatton July 2025

[Steven_Rice]

I believe that I checked every Texting component, and they were all set to OFF. Which makes sense, because I never changed that property for any component.

I might just be thinking too much here...

But, the only other thing I suspect is that I used the App Inventor 1 to App Inventor 2 conversion that you gracefully provided for us.

That doesn't fix my app. But, could I provide you with the . aia so you can check it out?

[Taifun]

@Steven_Rice

I checked every Texting component

There is no need to use several texting components, just use one

Taifun

[ewpatton]

@Steven_Rice

That doesn't fix my app. But, could I provide you with the . aia so you can check it out?

If you want to PM the AIA to me I can take a look.

[Steven_Rice]

In case anyone else wants to check it out:

HERESAFE.aia (183.4 KB)

[ewpatton]

When I compile your app it does not declare android.permission.RECEIVE_SMS. What is the exact rejection message from Google?

[Steven_Rice]

This is the email of denial. And, that is where I saw that it was requesting the RECEIVE_SMS permission.

[ewpatton]

Is it possible you're using an older AAB from before you fixed the problem? Try updating the VersionCode / VersionName and uploading a new build to Google Play.

[ewpatton]

And consider deleting any existing unpublished builds just in case.

[TIMAI2]

from the texting component code

Is the above sufficient to get Google's knickers in a twist ?

(I can see how the permission is granted if ReceiveEnabled != Off)

[ewpatton]

I guess I wouldn't past Google to be that dumb about substring matching that they are only looking for RECEIVE_SMS regardless of the qualified permission name. We probably should add a patch anyway that only adds those permissions if the GoogleVoiceEnabled flag is set.

[Steven_Rice]

TIMAI2,

 I appreciate you trying to help me with this.  But, I have no idea what your saying.

[TIMAI2]

@Steven_Rice

I have no idea what your saying.

Just exploring possible reasons for Google rejecting your app (looking at the source code for the texting component)

[Steven_Rice]

Roger that. Thanks for your time, I appreciate you looking into this for me.