Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

android.permission.READ_PHONE_STATE Requires Privacy Policy #50

Open
TechMindsYT opened this issue Feb 8, 2017 · 1 comment
Open

android.permission.READ_PHONE_STATE Requires Privacy Policy #50

TechMindsYT opened this issue Feb 8, 2017 · 1 comment

Comments

@TechMindsYT
Copy link

RadioPlayerService adds android.permission.READ_PHONE_STATE to final manifest. This causes an issue with requiring a Privacy Policy on the app listing.

What is the reason for requesting android.permission.READ_PHONE_STATE in the final Manifest and can it be removed?

@albedinsky
Copy link

The reason why the RadioPlayerService adds the android.permission.READ_PHONE_STATE may be found here at line 218. If you look at the phoneStateListener implementation, you will see that it handles changes in a call state of an Android device where the player service is running, and it stops the radio playback whenever there is an incoming/outgoing call, remembers that the playback has been active, and when the call ends, that listener will again start the radio playback for the current radio Url.

I think this is an obvious expected behavior as we do not want to interrupt a user's incoming/outgoing call with the Radio playback.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants