-
Notifications
You must be signed in to change notification settings - Fork 171
Why is android.permission.RECEIVE_SMS used in the manifest? (Hides app for tablets) #436
Comments
Hi @stefanhoth, the telephony feature is used for Fortumo. |
@akarimova I would like not to use this permission but since it's in the library it will be required automatically from an app that adds openIAB. Suggestion: You'll remove it from the manifest and check in the Furtomo part of the code if the permission exists, otherwise you throw an exception. So developers who implement Furtomo will add the permission into their app's manifest but other users won't be bothered. Sounds good? |
Wow, didn't see @RomanZhilich 's swift action yet. When is a new release planned that will include this fix? |
@stefanhoth.
in the end of the week Anyway, you can build the library using gradle |
As an alternative, you can use library as jar, instead of aar. It doesn't contain any resources, so the only difference should be manually declared manifest entries. |
@stefanhoth I haven't used this library yet but to prevent merging permissions I think you could also just add:
to your manifest file. |
@sdeff Thanks, that's indeed a nice workaround. But I think that a library shouldn't add those permissions in the first place. That's why I'm happy with the new way of handling this. |
@RomanZhilich I'm not sure this fix made it into the release. Could you clarify? |
@stefanhoth No, not yet. |
0.9.8.4 will be on this week |
In a project of ours we ran into an issue after using OpenIAB. Our app was unlisted from the Play Store for Tablets. Some investigation lead to the result that
android.permission.RECEIVE_SMS
(library/AndroidManifest#27 ) implicitly addsandroid.hardware.telephony require=true
.This is the fix that we needed to put in our app's manifest:
Question is: Why is this added to the library? Is it really needed? It's a rather privacy concerning permission that should be avoided if necessary. At the very least this should be treated optionally for the stores that require it.
The text was updated successfully, but these errors were encountered: