Some customers are complaining about the app requesting permission to read 
their phone calls, which obviously is in excess of what is actually needed. 
I've seen that there is an old discussion on the Android bug tracker about 
making READ_PHONE_STATE more fine grained to prevent this, but its not 
implemented.

There are apps that do push (and media) that don't request this permission 
and its a significant and concerning block of permissions to request if not 
totally needed.

I've seen an explanation that its needed to mute audio when there is an 
incoming call, but this doesn't seem to be the case there is this option:
https://developer.android.com/training/managing-audio/audio-focus.html

Why does including push also trigger this permission? - I believe you can 
get the push registration key in other ways. 

Also the reminder about the permission is shown before the the theme is 
loaded which makes it a mess if users decline it and this popup is shown, 
and it triggered before I register for push so I don't have the option to 
manage this at an appropriate place in the app flow, e.g., after you've 
logged in.

Having the first thing the app does is ask (twice) to make and read phone 
calls isn't very friendly!




-- 
You received this message because you are subscribed to the Google Groups 
"CodenameOne Discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
Visit this group at https://groups.google.com/group/codenameone-discussions.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/codenameone-discussions/346d77a4-82b4-4ade-9d10-8d7ce1789668%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to