Mixing
Permissions policy that will limit which apps are allowed to request Call Log and SMS permissions
Today I got a mail like this, according to this I’m not able to use RECEIVE_SMS READ_SMS anymore in my app. In my app I’m using auto read OTP. Is there any solution for this?
Hello Google Play Developer,
In October, we announced updates to our Permissions policy that will
limit which apps are allowed to request Call Log and SMS permissions.
This policy will impact one or more of your apps.
Only an app that has been selected as a user's default app for making
calls or text messages, or whose core functionality is approved for
one of the exception use cases, will be able to request access to Call
Log or SMS permissions.
Action required
Below, we've listed apps from your catalog which do not meet the
requirements for permission requests. Please remove any disallowed or
unused permissions from your app's manifest (specified below), migrate
to an alternative implementation (e.g. SMS Retriever API for most
cases of OTP verification), or evaluate if your app qualifies for an
exception.
Next steps
Read through the Permissions policy and the Play Console Help Center
article, which describes intended uses, exceptions, invalid uses, and
alternative implementation options for usage of Call Log or SMS
permissions.
Update your app or submit a Permissions Declaration Form.
Option 1) If your app does not require access to Call Log or SMS
permissions: Make appropriate changes to your app by removing the
specified permissions from your app's manifest or migrating to an
available alternative implementation by January 9, 2019.
Option 2) If your app is a default handler or you believe your app
qualifies for an exception: Please submit a request via the
Permissions Declaration Form. You do not need to have implemented APK
changes in order to submit a form. Declaration Forms received by
January 9, 2019 may be eligible for additional time to make changes to
bring their app(s) into compliance. If you have recently submitted a
Permissions Declaration Form, we are in the process of reviewing your
information and will respond to your application.
Make sure that your app is otherwise compliant with all other
Developer Program Policies to prevent your app from being removed.
Alternatively, you can choose to unpublish the app.
Our Developer Program Policies are designed to provide a safe and
secure experience for our users while also giving developers the tools
they need to succeed. That is why we will remove apps that violate our
policies. In cases of repeated or serious violations of our policies,
we may also terminate your developer account and any related developer
accounts.
We appreciate your willingness to partner with us as we make these
improvements to better protect users.
Affected apps
Affected apps and permissions are listed below, up to 20; if you have
additional apps, please ensure that they are also compliant with the
Permissions policy.
android 
google-play-services asked Nov 21 '18 at 4:53
AabauserAabauser
4212
add a comment |
Today I got a mail like this, according to this I’m not able to use RECEIVE_SMS READ_SMS anymore in my app. In my app I’m using auto read OTP. Is there any solution for this?
Hello Google Play Developer,
In October, we announced updates to our Permissions policy that will
limit which apps are allowed to request Call Log and SMS permissions.
This policy will impact one or more of your apps.
Only an app that has been selected as a user's default app for making
calls or text messages, or whose core functionality is approved for
one of the exception use cases, will be able to request access to Call
Log or SMS permissions.
Action required
Below, we've listed apps from your catalog which do not meet the
requirements for permission requests. Please remove any disallowed or
unused permissions from your app's manifest (specified below), migrate
to an alternative implementation (e.g. SMS Retriever API for most
cases of OTP verification), or evaluate if your app qualifies for an
exception.
Next steps
Read through the Permissions policy and the Play Console Help Center
article, which describes intended uses, exceptions, invalid uses, and
alternative implementation options for usage of Call Log or SMS
permissions.
Update your app or submit a Permissions Declaration Form.
Option 1) If your app does not require access to Call Log or SMS
permissions: Make appropriate changes to your app by removing the
specified permissions from your app's manifest or migrating to an
available alternative implementation by January 9, 2019.
Option 2) If your app is a default handler or you believe your app
qualifies for an exception: Please submit a request via the
Permissions Declaration Form. You do not need to have implemented APK
changes in order to submit a form. Declaration Forms received by
January 9, 2019 may be eligible for additional time to make changes to
bring their app(s) into compliance. If you have recently submitted a
Permissions Declaration Form, we are in the process of reviewing your
information and will respond to your application.
Make sure that your app is otherwise compliant with all other
Developer Program Policies to prevent your app from being removed.
Alternatively, you can choose to unpublish the app.
Our Developer Program Policies are designed to provide a safe and
secure experience for our users while also giving developers the tools
they need to succeed. That is why we will remove apps that violate our
policies. In cases of repeated or serious violations of our policies,
we may also terminate your developer account and any related developer
accounts.
We appreciate your willingness to partner with us as we make these
improvements to better protect users.
Affected apps
Affected apps and permissions are listed below, up to 20; if you have
additional apps, please ensure that they are also compliant with the
Permissions policy.
android google-play-services asked Nov 21 '18 at 4:53
AabauserAabauser
4212
Have you got the solution for this problem?
– Maaz Patel
Dec 17 '18 at 8:42
No, I submitted for the review but they rejected, so I decided to republish without auto detect OTP.
– Aabauser
Dec 18 '18 at 4:52
Do any of the following disallowed use cases apply to your app’s core functionality request for Call Log or SMS permissions? ..... What is mean by disallowed use cases? in Google Play Permissions Declaration Form.
– Mahesh Shahane
Dec 20 '18 at 6:59
Should I remove READ_SMS and RECEIVE_SMS permission? I am not available to upload my apk ! What should I do?
– Cristofer
Jan 28 at 17:30
Did you submitted for review?? if yes and they rejected then, If your app doesn't have the core functionality for Autodetect Sms either you remove READ_SMS and RECEIVE_SMS and republish or use the below solutions
– Aabauser
yesterday
add a comment |
Today I got a mail like this, according to this I’m not able to use RECEIVE_SMS READ_SMS anymore in my app. In my app I’m using auto read OTP. Is there any solution for this?
Hello Google Play Developer,
In October, we announced updates to our Permissions policy that will
limit which apps are allowed to request Call Log and SMS permissions.
This policy will impact one or more of your apps.
Only an app that has been selected as a user's default app for making
calls or text messages, or whose core functionality is approved for
one of the exception use cases, will be able to request access to Call
Log or SMS permissions.
Action required
Below, we've listed apps from your catalog which do not meet the
requirements for permission requests. Please remove any disallowed or
unused permissions from your app's manifest (specified below), migrate
to an alternative implementation (e.g. SMS Retriever API for most
cases of OTP verification), or evaluate if your app qualifies for an
exception.
Next steps
Read through the Permissions policy and the Play Console Help Center
article, which describes intended uses, exceptions, invalid uses, and
alternative implementation options for usage of Call Log or SMS
permissions.
Update your app or submit a Permissions Declaration Form.
Option 1) If your app does not require access to Call Log or SMS
permissions: Make appropriate changes to your app by removing the
specified permissions from your app's manifest or migrating to an
available alternative implementation by January 9, 2019.
Option 2) If your app is a default handler or you believe your app
qualifies for an exception: Please submit a request via the
Permissions Declaration Form. You do not need to have implemented APK
changes in order to submit a form. Declaration Forms received by
January 9, 2019 may be eligible for additional time to make changes to
bring their app(s) into compliance. If you have recently submitted a
Permissions Declaration Form, we are in the process of reviewing your
information and will respond to your application.
Make sure that your app is otherwise compliant with all other
Developer Program Policies to prevent your app from being removed.
Alternatively, you can choose to unpublish the app.
Our Developer Program Policies are designed to provide a safe and
secure experience for our users while also giving developers the tools
they need to succeed. That is why we will remove apps that violate our
policies. In cases of repeated or serious violations of our policies,
we may also terminate your developer account and any related developer
accounts.
We appreciate your willingness to partner with us as we make these
improvements to better protect users.
Affected apps
Affected apps and permissions are listed below, up to 20; if you have
additional apps, please ensure that they are also compliant with the
Permissions policy.
android google-play-services asked Nov 21 '18 at 4:53
AabauserAabauser
4212
Today I got a mail like this, according to this I’m not able to use RECEIVE_SMS READ_SMS anymore in my app. In my app I’m using auto read OTP. Is there any solution for this?
Hello Google Play Developer,
In October, we announced updates to our Permissions policy that will
limit which apps are allowed to request Call Log and SMS permissions.
This policy will impact one or more of your apps.
Only an app that has been selected as a user's default app for making
calls or text messages, or whose core functionality is approved for
one of the exception use cases, will be able to request access to Call
Log or SMS permissions.
Action required
Below, we've listed apps from your catalog which do not meet the
requirements for permission requests. Please remove any disallowed or
unused permissions from your app's manifest (specified below), migrate
to an alternative implementation (e.g. SMS Retriever API for most
cases of OTP verification), or evaluate if your app qualifies for an
exception.
Next steps
Read through the Permissions policy and the Play Console Help Center
article, which describes intended uses, exceptions, invalid uses, and
alternative implementation options for usage of Call Log or SMS
permissions.
Update your app or submit a Permissions Declaration Form.
Option 1) If your app does not require access to Call Log or SMS
permissions: Make appropriate changes to your app by removing the
specified permissions from your app's manifest or migrating to an
available alternative implementation by January 9, 2019.
Option 2) If your app is a default handler or you believe your app
qualifies for an exception: Please submit a request via the
Permissions Declaration Form. You do not need to have implemented APK
changes in order to submit a form. Declaration Forms received by
January 9, 2019 may be eligible for additional time to make changes to
bring their app(s) into compliance. If you have recently submitted a
Permissions Declaration Form, we are in the process of reviewing your
information and will respond to your application.
Make sure that your app is otherwise compliant with all other
Developer Program Policies to prevent your app from being removed.
Alternatively, you can choose to unpublish the app.
Our Developer Program Policies are designed to provide a safe and
secure experience for our users while also giving developers the tools
they need to succeed. That is why we will remove apps that violate our
policies. In cases of repeated or serious violations of our policies,
we may also terminate your developer account and any related developer
accounts.
We appreciate your willingness to partner with us as we make these
improvements to better protect users.
Affected apps
Affected apps and permissions are listed below, up to 20; if you have
additional apps, please ensure that they are also compliant with the
Permissions policy.
android google-play-services android google-play-services asked Nov 21 '18 at 4:53
AabauserAabauser
4212
asked Nov 21 '18 at 4:53
AabauserAabauser
4212
asked Nov 21 '18 at 4:53
AabauserAabauser
4212
asked Nov 21 '18 at 4:53
AabauserAabauser
4212
asked Nov 21 '18 at 4:53
AabauserAabauser
4212
4212
Have you got the solution for this problem?
– Maaz Patel
Dec 17 '18 at 8:42
No, I submitted for the review but they rejected, so I decided to republish without auto detect OTP.
– Aabauser
Dec 18 '18 at 4:52
Do any of the following disallowed use cases apply to your app’s core functionality request for Call Log or SMS permissions? ..... What is mean by disallowed use cases? in Google Play Permissions Declaration Form.
– Mahesh Shahane
Dec 20 '18 at 6:59
Should I remove READ_SMS and RECEIVE_SMS permission? I am not available to upload my apk ! What should I do?
– Cristofer
Jan 28 at 17:30
Did you submitted for review?? if yes and they rejected then, If your app doesn't have the core functionality for Autodetect Sms either you remove READ_SMS and RECEIVE_SMS and republish or use the below solutions
– Aabauser
yesterday
add a comment |
Have you got the solution for this problem?
– Maaz Patel
Dec 17 '18 at 8:42
No, I submitted for the review but they rejected, so I decided to republish without auto detect OTP.
– Aabauser
Dec 18 '18 at 4:52
Do any of the following disallowed use cases apply to your app’s core functionality request for Call Log or SMS permissions? ..... What is mean by disallowed use cases? in Google Play Permissions Declaration Form.
– Mahesh Shahane
Dec 20 '18 at 6:59
Should I remove READ_SMS and RECEIVE_SMS permission? I am not available to upload my apk ! What should I do?
– Cristofer
Jan 28 at 17:30
Did you submitted for review?? if yes and they rejected then, If your app doesn't have the core functionality for Autodetect Sms either you remove READ_SMS and RECEIVE_SMS and republish or use the below solutions
– Aabauser
yesterday
Have you got the solution for this problem?
– Maaz Patel
Dec 17 '18 at 8:42
Have you got the solution for this problem?
– Maaz Patel
Dec 17 '18 at 8:42
No, I submitted for the review but they rejected, so I decided to republish without auto detect OTP.
– Aabauser
Dec 18 '18 at 4:52
No, I submitted for the review but they rejected, so I decided to republish without auto detect OTP.
– Aabauser
Dec 18 '18 at 4:52
Do any of the following disallowed use cases apply to your app’s core functionality request for Call Log or SMS permissions? ..... What is mean by disallowed use cases? in Google Play Permissions Declaration Form.
– Mahesh Shahane
Dec 20 '18 at 6:59
Do any of the following disallowed use cases apply to your app’s core functionality request for Call Log or SMS permissions? ..... What is mean by disallowed use cases? in Google Play Permissions Declaration Form.
– Mahesh Shahane
Dec 20 '18 at 6:59
Should I remove READ_SMS and RECEIVE_SMS permission? I am not available to upload my apk ! What should I do?
– Cristofer
Jan 28 at 17:30
Should I remove READ_SMS and RECEIVE_SMS permission? I am not available to upload my apk ! What should I do?
– Cristofer
Jan 28 at 17:30
Did you submitted for review?? if yes and they rejected then, If your app doesn't have the core functionality for Autodetect Sms either you remove READ_SMS and RECEIVE_SMS and republish or use the below solutions
– Aabauser
yesterday
Did you submitted for review?? if yes and they rejected then, If your app doesn't have the core functionality for Autodetect Sms either you remove READ_SMS and RECEIVE_SMS and republish or use the below solutions
– Aabauser
yesterday
add a comment |
3 Answers
3
active
oldest
votes
this one is also a solution.. without submitting form we have another solution .. for this we need to genarate app id..
SMS Retriever Api
answered Nov 24 '18 at 12:14
satyan_androidsatyan_android
788
add a comment |
Its not like that you are thinking about. Go to this link
and fill up and submit the from. If you app's default function is to show SMS inbox or just OTP account verification, then they will not remove your app.
answered Nov 21 '18 at 6:29
SHAH MD MONIRUL ISLAMSHAH MD MONIRUL ISLAM
1,46531530
add a comment |
Google is no more allowing more apps with SMS permission due to security and privacy issue. So if you need Phone No verification then
Firebase Auth is the best option. It's almost free
Limit:Verification code SMS messages 50 messages/IP address/minute, 500 messages/IP address/hour
https://firebase.google.com/docs/auth/android/phone-auth
answered Jan 8 at 17:16
Rajesh NasitRajesh Nasit
2,06011725
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53405467%2fpermissions-policy-that-will-limit-which-apps-are-allowed-to-request-call-log-an%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
this one is also a solution.. without submitting form we have another solution .. for this we need to genarate app id..
SMS Retriever Api
answered Nov 24 '18 at 12:14
satyan_androidsatyan_android
788
add a comment |
this one is also a solution.. without submitting form we have another solution .. for this we need to genarate app id..
SMS Retriever Api
answered Nov 24 '18 at 12:14
satyan_androidsatyan_android
788
add a comment |
this one is also a solution.. without submitting form we have another solution .. for this we need to genarate app id..
SMS Retriever Api
answered Nov 24 '18 at 12:14
satyan_androidsatyan_android
788
this one is also a solution.. without submitting form we have another solution .. for this we need to genarate app id..
SMS Retriever Api
answered Nov 24 '18 at 12:14
satyan_androidsatyan_android
788
answered Nov 24 '18 at 12:14
satyan_androidsatyan_android
788
answered Nov 24 '18 at 12:14
satyan_androidsatyan_android
788
answered Nov 24 '18 at 12:14
satyan_androidsatyan_android
788
788
add a comment |
add a comment |
Its not like that you are thinking about. Go to this link
and fill up and submit the from. If you app's default function is to show SMS inbox or just OTP account verification, then they will not remove your app.
answered Nov 21 '18 at 6:29
SHAH MD MONIRUL ISLAMSHAH MD MONIRUL ISLAM
1,46531530
add a comment |
Its not like that you are thinking about. Go to this link
and fill up and submit the from. If you app's default function is to show SMS inbox or just OTP account verification, then they will not remove your app.
answered Nov 21 '18 at 6:29
SHAH MD MONIRUL ISLAMSHAH MD MONIRUL ISLAM
1,46531530
add a comment |
Its not like that you are thinking about. Go to this link
and fill up and submit the from. If you app's default function is to show SMS inbox or just OTP account verification, then they will not remove your app.
answered Nov 21 '18 at 6:29
SHAH MD MONIRUL ISLAMSHAH MD MONIRUL ISLAM
1,46531530
Its not like that you are thinking about. Go to this link
and fill up and submit the from. If you app's default function is to show SMS inbox or just OTP account verification, then they will not remove your app.
answered Nov 21 '18 at 6:29
SHAH MD MONIRUL ISLAMSHAH MD MONIRUL ISLAM
1,46531530
answered Nov 21 '18 at 6:29
SHAH MD MONIRUL ISLAMSHAH MD MONIRUL ISLAM
1,46531530
answered Nov 21 '18 at 6:29
SHAH MD MONIRUL ISLAMSHAH MD MONIRUL ISLAM
1,46531530
answered Nov 21 '18 at 6:29
SHAH MD MONIRUL ISLAMSHAH MD MONIRUL ISLAM
1,46531530
1,46531530
add a comment |
add a comment |
Google is no more allowing more apps with SMS permission due to security and privacy issue. So if you need Phone No verification then
Firebase Auth is the best option. It's almost free
Limit:Verification code SMS messages 50 messages/IP address/minute, 500 messages/IP address/hour
https://firebase.google.com/docs/auth/android/phone-auth
answered Jan 8 at 17:16
Rajesh NasitRajesh Nasit
2,06011725
add a comment |
Google is no more allowing more apps with SMS permission due to security and privacy issue. So if you need Phone No verification then
Firebase Auth is the best option. It's almost free
Limit:Verification code SMS messages 50 messages/IP address/minute, 500 messages/IP address/hour
https://firebase.google.com/docs/auth/android/phone-auth
answered Jan 8 at 17:16
Rajesh NasitRajesh Nasit
2,06011725
add a comment |
Google is no more allowing more apps with SMS permission due to security and privacy issue. So if you need Phone No verification then
Firebase Auth is the best option. It's almost free
Limit:Verification code SMS messages 50 messages/IP address/minute, 500 messages/IP address/hour
https://firebase.google.com/docs/auth/android/phone-auth
answered Jan 8 at 17:16
Rajesh NasitRajesh Nasit
2,06011725
Google is no more allowing more apps with SMS permission due to security and privacy issue. So if you need Phone No verification then
Firebase Auth is the best option. It's almost free
Limit:Verification code SMS messages 50 messages/IP address/minute, 500 messages/IP address/hour
https://firebase.google.com/docs/auth/android/phone-auth
answered Jan 8 at 17:16
Rajesh NasitRajesh Nasit
2,06011725
answered Jan 8 at 17:16
Rajesh NasitRajesh Nasit
2,06011725
answered Jan 8 at 17:16
Rajesh NasitRajesh Nasit
2,06011725
answered Jan 8 at 17:16
Rajesh NasitRajesh Nasit
2,06011725
2,06011725
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53405467%2fpermissions-policy-that-will-limit-which-apps-are-allowed-to-request-call-log-an%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Have you got the solution for this problem?
– Maaz Patel
Dec 17 '18 at 8:42
No, I submitted for the review but they rejected, so I decided to republish without auto detect OTP.
– Aabauser
Dec 18 '18 at 4:52
Do any of the following disallowed use cases apply to your app’s core functionality request for Call Log or SMS permissions? ..... What is mean by disallowed use cases? in Google Play Permissions Declaration Form.
– Mahesh Shahane
Dec 20 '18 at 6:59
Should I remove READ_SMS and RECEIVE_SMS permission? I am not available to upload my apk ! What should I do?
– Cristofer
Jan 28 at 17:30
Did you submitted for review?? if yes and they rejected then, If your app doesn't have the core functionality for Autodetect Sms either you remove READ_SMS and RECEIVE_SMS and republish or use the below solutions
– Aabauser
yesterday