Publikacja aplikacji mobilnej na rynku (AppStore/PlayMarket)

Natalya Seocore Team 19 października 2022

опис помилки в гуглмаркеті

Hi Developers at LLC ULS,

After a recent review, we found that your app Care4You (com.uppercode.careforyou) is not compliant with one or more of our Developer Program Policies. See below for more information about your app's status and how to correct the issue.

App Status: Rejected Your app has been rejected and wasn't published due to the policy issue(s) listed below. If you submitted an update, the previous version of your app is still available on Google Play.

Issue found: Feature does not meet requirements for background location access Based on our review, your declared feature does not meet the requirements for background location access. Please remove the background location permission requested and submit an update to your app. When declaring a feature for background location access, please note the following: Your selected feature should deliver clear value to the user and be important to the core functionality, or main purpose of the app. Without this core feature, the app is "broken" or rendered unusable. You should also consider if users would expect the app to access their location in the background, and if you can deliver the same experience without accessing location in the background. About the Permissions and APIs that Access Sensitive Information Policy Requests for permission and APIs that access sensitive information should make sense to users. You may only request permissions and APIs that access sensitive information that are necessary to implement current features or services in your app that are promoted in your Google Play listing. You may not use permissions or APIs that access sensitive information that give access to user or device data for undisclosed, unimplemented, or disallowed features or purposes. Personal or sensitive data accessed through permissions or APIs that access sensitive information may never be sold. Request permissions and APIs that access sensitive information to access data in context (via incremental requests), so that users understand why your app is requesting the permission. Use the data only for purposes that the user has consented to. If you later wish to use the data for other purposes, you must ask users and make sure they affirmatively agree to the additional uses. Read through the Permissions and APIs that Access Sensitive Information policy, Location Permissionspolicy, and Help Center article for more information.

Issue found: Prominent disclosure not found Your app must display a prominent disclosure through a pop-up alert before your app’s location runtime permission. Based on our review, a prominent disclosure did not appear before the runtime permission. Please add a prominent disclosure before the runtime permission. To meet the policy requirements, it’s recommended that you reference one of the following example formats, the second example includes the use of location for ads (choose the most relevant phrasing): “[This app] collects location data to enable [“feature“], [“feature“], & [“feature“] even when the app is closed or not in use.” “[This app] collects location data to enable [“feature“], [“feature“], & [“feature“] even when the app is closed or not in use and it is also used to support advertising.” Example: “Fitness Funds collects location data to enable fitness tracking even when the app is closed or not in use.” The language in the disclosure MUST include the following elements: The term “location” Indication that the nature of usage is in the background by using one of the following phrases “background” / “when the app is closed” / “always in use” / “when the app is not in use” A list of all the features that use location in the background If you extend permitted usage to ads, you must include the following: “used to provide ads / support advertising / support ads.” (Choose the most accurate phrasing) Remember, your prominent disclosure must: Appear before your app’s location runtime permission Include an example format listed above Include any other details necessary to make it clear to the user how and why you are using location in the background. While additional content is permitted, it should not cause the required content to not be immediately visible Include buttons that are clear to the user if they are approving or denying access. If a user denies access and that would limit the app experience, then make sure to inform them on how to change preferences in the future Not appear alongside other data privacy disclosures or as part of the privacy policy Please ensure your prominent disclosure is included in the video required in the Developer console. Learn more about prominent disclosure requirements in the Developer Policy Center or in this video. About the Permissions and APIs that Access Sensitive Information Policy Requests for permission and APIs that access sensitive information should make sense to users. You may only request permissions and APIs that access sensitive information that are necessary to implement current features or services in your app that are promoted in your Google Play listing. You may not use permissions or APIs that access sensitive information that give access to user or device data for undisclosed, unimplemented, or disallowed features or purposes. Personal or sensitive data accessed through permissions or APIs that access sensitive information may never be sold. Request permissions and APIs that access sensitive information to access data in context (via incremental requests), so that users understand why your app is requesting the permission. Use the data only for purposes that the user has consented to. If you later wish to use the data for other purposes, you must ask users and make sure they affirmatively agree to the additional uses. Read through the Permissions and APIs that Access Sensitive Information policy, Location Permissionspolicy, and Help Center article for more information.

Natalya Seocore Team 19 października 2022

опис помилки в гуглмаркеті

Hi Developers at LLC ULS,

After a recent review, we found that your app Care4You (com.uppercode.careforyou) is not compliant with one or more of our Developer Program Policies. See below for more information about your app's status and how to correct the issue.

App Status: Rejected Your app has been rejected and wasn't published due to the policy issue(s) listed below. If you submitted an update, the previous version of your app is still available on Google Play.

Issue found: Feature does not meet requirements for background location access Based on our review, your declared feature does not meet the requirements for background location access. Please remove the background location permission requested and submit an update to your app. When declaring a feature for background location access, please note the following: Your selected feature should deliver clear value to the user and be important to the core functionality, or main purpose of the app. Without this core feature, the app is "broken" or rendered unusable. You should also consider if users would expect the app to access their location in the background, and if you can deliver the same experience without accessing location in the background. About the Permissions and APIs that Access Sensitive Information Policy Requests for permission and APIs that access sensitive information should make sense to users. You may only request permissions and APIs that access sensitive information that are necessary to implement current features or services in your app that are promoted in your Google Play listing. You may not use permissions or APIs that access sensitive information that give access to user or device data for undisclosed, unimplemented, or disallowed features or purposes. Personal or sensitive data accessed through permissions or APIs that access sensitive information may never be sold. Request permissions and APIs that access sensitive information to access data in context (via incremental requests), so that users understand why your app is requesting the permission. Use the data only for purposes that the user has consented to. If you later wish to use the data for other purposes, you must ask users and make sure they affirmatively agree to the additional uses. Read through the Permissions and APIs that Access Sensitive Information policy, Location Permissionspolicy, and Help Center article for more information.

Issue found: Prominent disclosure not found Your app must display a prominent disclosure through a pop-up alert before your app’s location runtime permission. Based on our review, a prominent disclosure did not appear before the runtime permission. Please add a prominent disclosure before the runtime permission. To meet the policy requirements, it’s recommended that you reference one of the following example formats, the second example includes the use of location for ads (choose the most relevant phrasing): “[This app] collects location data to enable [“feature“], [“feature“], & [“feature“] even when the app is closed or not in use.” “[This app] collects location data to enable [“feature“], [“feature“], & [“feature“] even when the app is closed or not in use and it is also used to support advertising.” Example: “Fitness Funds collects location data to enable fitness tracking even when the app is closed or not in use.” The language in the disclosure MUST include the following elements: The term “location” Indication that the nature of usage is in the background by using one of the following phrases “background” / “when the app is closed” / “always in use” / “when the app is not in use” A list of all the features that use location in the background If you extend permitted usage to ads, you must include the following: “used to provide ads / support advertising / support ads.” (Choose the most accurate phrasing) Remember, your prominent disclosure must: Appear before your app’s location runtime permission Include an example format listed above Include any other details necessary to make it clear to the user how and why you are using location in the background. While additional content is permitted, it should not cause the required content to not be immediately visible Include buttons that are clear to the user if they are approving or denying access. If a user denies access and that would limit the app experience, then make sure to inform them on how to change preferences in the future Not appear alongside other data privacy disclosures or as part of the privacy policy Please ensure your prominent disclosure is included in the video required in the Developer console. Learn more about prominent disclosure requirements in the Developer Policy Center or in this video. About the Permissions and APIs that Access Sensitive Information Policy Requests for permission and APIs that access sensitive information should make sense to users. You may only request permissions and APIs that access sensitive information that are necessary to implement current features or services in your app that are promoted in your Google Play listing. You may not use permissions or APIs that access sensitive information that give access to user or device data for undisclosed, unimplemented, or disallowed features or purposes. Personal or sensitive data accessed through permissions or APIs that access sensitive information may never be sold. Request permissions and APIs that access sensitive information to access data in context (via incremental requests), so that users understand why your app is requesting the permission. Use the data only for purposes that the user has consented to. If you later wish to use the data for other purposes, you must ask users and make sure they affirmatively agree to the additional uses. Read through the Permissions and APIs that Access Sensitive Information policy, Location Permissionspolicy, and Help Center article for more information.