You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 28, 2022. It is now read-only.
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 adds android.hardware.telephony require=true.
This is the fix that we needed to put in our app's manifest:
<!-- telephony required=true is implicit from the RECEIVE_SMS permission in openIAB -->
<uses-feature
android:name="android.hardware.telephony"
android:required="false" />
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.
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.