Skip to content
This repository has been archived by the owner on Oct 22, 2022. It is now read-only.

[Major Issue] Revocation of app from playstore #72

Open
dig22 opened this issue Feb 24, 2019 · 3 comments
Open

[Major Issue] Revocation of app from playstore #72

dig22 opened this issue Feb 24, 2019 · 3 comments

Comments

@dig22
Copy link

dig22 commented Feb 24, 2019

Application Relocated from PlayStore due to dangerous use of
<uses-permission android:name="android.permission.CALL_PHONE" />

@ppetree
Copy link

ppetree commented Mar 10, 2019

Any resolution on this?

@hnguyen48206
Copy link

I'm in need of a good solution to address this matter too. My app has recently been rejected by Google. This is the message I got: "After review, we found that your app does not qualify for use of the requested permissions. In your permissions declaration form, you had indicated that your app is a default handler; however, we were unable to detect that capability in your app’s manifest."

@dig22
Copy link
Author

dig22 commented Mar 16, 2019

I can propose a temporary solution to this by using InAppBrowser (Cordova Plugin) or Links within app by using the tel: prefix on links.

this.iab.create('tel:'+ <TELEPHONE NUMBER> , '_system');
OR
<a href="tel:<TELEPHONE NUMBER>:">Call : <TELEPHONE NUMBER></a>

which opens the Dialer with the number on phones.

NOTE : CordovaCallNumber should be uninstalled so it doesn't add the CALL_PHONE permission.

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

No branches or pull requests

3 participants