Apps Google play: This app requires direct phone access and can make calls without asking first

[werner291]

Hello, I've just published an app to Google Play. It is an app that allows people (mostly tourists) in my area to easely find businesses around them. One functinality that my app offers is to make a phone call to these companies by tapping a button in the app, including emergency numbers.

Because of this, Google Play says that the app requires "direct phone acess, it can call phone numbers without your intervention, which can lead to a high phone bill, but not emergency numbers". This doesn't completely fit my intention.

My app would work just fine if it had to ask the user every time it wanted to make a call, and it doesn't call anything when no buttons are tapped, plus I DO want the app to be able to call emergency numbers (with the user's conscent off course), so what am I supposed to put in my app manifest to correct this?

 

[gtbarry]

Just say what you did above in the app description.

I think a lot of people don't read the details of permissions or care too much about what they say. It basically comes down to whether or not you trust the app/developer. I spend more time reading the app description and comments/reviews than I do the actual permissions. If your app were to run up bills it would be all over your comments.

 

[ExtremeNerd]

Moved to the Development thread so you can get answers from the people who know best.

Just say what you did above in the app description.

I think a lot of people don't read the details of permissions or care too much about what they say. It basically comes down to whether or not you trust the app/developer. I spend more time reading the app description and comments/reviews than I do the actual permissions. If your app were to run up bills it would be all over your comments.

Unfortunately, this is true. Permissions are the one thing you should always read before downloading an app. Things are generally safe from Google Play, but rogue apps have made it before. However, when I see a flashlight app that needs access to contacts, phone logs, and sending SMS, I'm avoiding it at all costs.

As to the OP problem, I'm going to assume it has everything to do with the permissions you declared. Maybe there is another declaration you need to make instead. Or at the very least, explain it in your description. That may be Google's default description for a permission. It's a blanket statement that may not fit what you exactly programmed the app to do.

If I find questionable permissions on an app, and there is no validation, no downloading for me. Justify it and you should have no trouble.

 

[werner291]

Ok, I added it in the description. How about emergency numbers? Does it just raise a security exception or will it ask the user wether to make the call? If it's the first one, is there any way to still call emergency numbers? (My app is likely to be used by foreigners who might not know the emergency numbers in my country, so I'm including a tap-to-call button, but is that even possible?)

 

[ymas086]

how about you just make it so that the tap call button can just access the default call handler. This way you can make it so the URI would contain the appropriate phone number as well as bypass the need for a description on the permission??