#
closed
the app is rejected from google play

hithe app got rejected from google play twice , how to fix this issue 

Your app is using the Cardinal Commerce SDK which collects but may not be limited to Android ID and Hardware IDs identifiers. Persistent device identifiers may not be linked to other personal and sensitive user data or resettable device identifiers.You may consider moving to another SDK; removing this SDK; or if available from your SDK provider, upgrading to a policy-compliant version of this SDK that does not include the violating code.According to the information provided by your SDK provider, you may consider upgrading to 2.2.7-2. Please consult the SDK provider for further information.Affected Version(s):App Bundle:11, App Bundle:11, App Bundle:11, App Bundle:9, App Bundle:9
Your app is using the Cardinal Commerce SDK which collects but may not be limited to Android ID and Hardware IDs identifiers. Persistent device identifiers may not be linked to other personal and sensitive user data or resettable device identifiers.You may consider moving to another SDK; removing this SDK; or if available from your SDK provider, upgrading to a policy-compliant version of this SDK that does not include the violating code.According to the information provided by your SDK provider, you may consider upgrading to 2.2.7-2. Please consult the SDK provider for further information.Affected Version(s):App Bundle:11, App Bundle:11, App Bundle:11, App Bundle:9, App Bundle:9
Reasons of violation
Your app is using the Cardinal Commerce SDK which collects but may not be limited to Android ID and Hardware IDs identifiers. Persistent device identifiers may not be linked to other personal and sensitive user data or resettable device identifiers.You may consider moving to another SDK; removing this SDK; or if available from your SDK provider, upgrading to a policy-compliant version of this SDK that does not include the violating code.According to the information provided by your SDK provider, you may consider upgrading to 2.2.7-2. Please consult the SDK provider for further information.Affected Version(s):App Bundle:11, App Bundle:11, App Bundle:11, App Bundle:9, App Bundle:9
About the User Data policy
Limit the access, collection, use, and sharing of personal and sensitive user data acquired through the app to app and service functionality and policy conforming purposes reasonably expected by the user.Persistent device identifiers may not be linked to other personal and sensitive user data or resettable device identifiers except for the purposes of:Telephony linked to a SIM identity (e.g., wifi calling linked to a carrier account), andEnterprise device management apps using device owner mode.These uses must be prominently disclosed to users as specified in the User Data policy. Please consult this resource for alternative unique identifiers.
Your app is using the Cardinal Commerce SDK which collects but may not be limited to Android ID and Hardware IDs identifiers. Persistent device identifiers may not be linked to other personal and sensitive user data or resettable device identifiers.You may consider moving to another SDK; removing this SDK; or if available from your SDK provider, upgrading to a policy-compliant version of this SDK that does not include the violating code.According to the information provided by your SDK provider, you may consider upgrading to 2.2.7-2. Please consult the SDK provider for further information.Affected Version(s):App Bundle:11, App Bundle:11, App Bundle:11, App Bundle:9, App Bundle:9
Publishing Status
Your app is using the Cardinal Commerce SDK which collects but may not be limited to Android ID and Hardware IDs identifiers. Persistent device identifiers may not be linked to other personal and sensitive user data or resettable device identifiers.You may consider moving to another SDK; removing this SDK; or if available from your SDK provider, upgrading to a policy-compliant version of this SDK that does not include the violating code.According to the information provided by your SDK provider, you may consider upgrading to 2.2.7-2. Please consult the SDK provider for further information.Affected Version(s):App Bundle:11, App Bundle:11, App Bundle:11, App Bundle:9, App Bundle:9
App status: Rejected
Your app has been rejected and wasn't published due to this policy issue. If you submitted an update, the previous version of your app is still available on Google Play.

Asked 2 years ago on April 29, 2023 11:51 PM Comments 8 times


  1. Generic placeholder image

    Flora replied

    Hello,

    This issue occurs because of using the Braintree payment gateway. We applied this solution and uploaded it to the play store and it's perfectly working.

    flutter_braintree payment gateway issue solution:

    https://github.com/pikaju/flutter-braintree/issues/129

    Please fill data safety form again and make aab again and upload it to the Play Store.

    Thanks & Regards

    - Flora
  2. Generic placeholder image

    Specter Hassan replied

    dear I already made this edit, that was your first replay on this ticket and after that, I uploaded another version and I got the same rejection , so kindly advise me on what I could try next 

  3. Generic placeholder image

    Flora replied

    Hello,
     
    Open android/app/build.gradle file and add these lines in dependencies. Then make aab file and upload it to playstore.
     
    implementation('com.braintreepayments.api:drop-in:5.2.1'){
          exclude group: "org.jfrog.cardinalcommerce.gradle", module: "cardinalmobilesdk"
    }
    implementation("org.jfrog.cardinalcommerce.gradle:cardinalmobilesdk:2.2.7-2")
     
    Thanks & Regards

    - Flora

    ATTACHED FILES

  4. Generic placeholder image

    Specter Hassan replied

    thank you for your fast replay, kindly advise on the other two rejection reasons 

     

    reasons 2

    issue with your app 

    Your app is using the Cardinal Commerce SDK which collects but may not be limited to Android ID and Hardware IDs identifiers. Persistent device identifiers may not be linked to other personal and sensitive user data or resettable device identifiers.

    You may consider moving to another SDK; removing this SDK; or if available from your SDK provider, upgrading to a policy-compliant version of this SDK that does not include the violating code.

    According to the information provided by your SDK provider, you may consider upgrading to 2.2.7-2. Please consult the SDK provider for further information.

    Affected Version(s):

    App Bundle:9, App Bundle:9

     

    About the User Data policy

    Limit the access, collection, use, and sharing of personal and sensitive user data acquired through the app to app and service functionality and policy conforming purposes reasonably expected by the user.

    Persistent device identifiers may not be linked to other personal and sensitive user data or resettable device identifiers except for the purposes of:

    • Telephony linked to a SIM identity (e.g., wifi calling linked to a carrier account), and
    • Enterprise device management apps using device owner mode.

    These uses must be prominently disclosed to users as specified in the User Data policy. Please consult this resource for alternative unique identifiers.

     

    App status: Rejected

    Your app has been rejected and wasn't published due to this policy issue. If you submitted an update, the previous version of your app is still available on Google Play.




    reason 3



     

    Issue with your app

    Your app is using the Cardinal Mobile SDK which collects persistent device identifiers, but may not be limited to Android ID and hardware IDs. Persistent device identifiers may not be linked to any other personal and sensitive user data and/or resettable device identifiers (e.g., IMEI, IMSI, SIM Serial #, etc).

    You may consider upgrading to a policy-compliant version of this SDK, if available from your SDK provider or removing the SDK. According to your SDK provider, you may consider upgrading to 2.2.7-2. Please consult the SDK provider for further information. Google is unable to endorse or recommend any third party software.

     

    About the User Data policy

    If an app handles personal and sensitive user data, then the app developer must limit the access, collection, use, and sharing of personal and sensitive user data acquired through the app to app and service functionality and policy conforming purposes reasonably expected by the user.

    Persistent device identifiers may not be linked to other personal and sensitive user data or resettable device identifiers except for the purposes of:

    • Telephony linked to a SIM identity (e.g., wifi calling linked to a carrier account), and
    • Enterprise device management apps using device owner mode.

    These uses must be prominently disclosed to users as specified in the User Data policy. Please consult this resource for alternative unique identifiers.

  5. Generic placeholder image

    Flora replied

    Hello Specter Hassan,

    Your application is rejected because of a data safety issue. Fill data safety section again and check it.

    Thanks & Regards

    - Flora
  6. Generic placeholder image

    Specter Hassan replied

    Hi the app got rejected again 

    now for 3 reasons 

     

    reason 1

    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:

    Invalid Data safety form

    We reviewed your app’s Data safety form in Play Console and found discrepancies between it and how the app collects and shares user data. All apps are required to complete an accurate Data safety form that discloses their data collection and sharing practices - this is required even if your app does not collect any user data.

    We detected user data transmitted off device that you have not disclosed in your app’s Data safety form as user data collected.

    You must ensure that your app’s Data safety section accurately reflects your app’s data collection, sharing, and handling practices. This includes data collected and handled through any third-party libraries or SDKs used in your app. When available, we’ve included details on SDKs that contain code similar to the code in your APK that may be sending user data off device. You can check if your app uses any of these SDKs, but note that this list of SDKs may not be exhaustive. You must review and account for all data collected and shared by your app.

    Issue details

    We found an issue in the following area(s):

    • SPLIT_BUNDLE 9: Policy Declaration - Data Safety Section: Device Or Other IDs Data Type - Device Or Other IDs (some common examples may include Advertising ID, Android ID, IMEI, BSSID, MAC address)
    • SPLIT_BUNDLE 9: Policy Declaration - Data Safety Section: Location Data Type - Precise Location
    • SPLIT_BUNDLE 15: Policy Declaration - Data Safety Section: Device Or Other IDs Data Type - Device Or Other IDs (some common examples may include Advertising ID, Android ID, IMEI, BSSID, MAC address)
    • SPLIT_BUNDLE 15: Policy Declaration - Data Safety Section: Location Data Type - Precise Location

    About the Data safety section in Google Play User Data policy

    Your app must be in compliance with this policy. If your app continues to be non-compliant, your app updates will be rejected and your app may face additional enforcement actions in the future.

    Please make changes to align your app’s Data safety form with the app’s behavior. This can be done by either:

    • Updating your form in Play Console to declare collection of Data Types noted below; or
    • Removing unwanted functionality and attributable code that collects this user data from your app or libraries used in your app, and when applicable to deactivate all non-compliant APKs.
      • To deactivate non-compliant APKS, you can create a new release and upload a compliant APK to each track containing the non-compliant APKs.
      • Be sure to increment the APK version code. If using staged rollout, be sure to set the release to 100% rollout.

    For helpful resources, you can:

     

    reason 2


    Issue with your app 

    Your app is using the Cardinal Commerce SDK which collects but may not be limited to Android ID and Hardware IDs identifiers. Persistent device identifiers may not be linked to other personal and sensitive user data or resettable device identifiers.

    You may consider moving to another SDK; removing this SDK; or if available from your SDK provider, upgrading to a policy-compliant version of this SDK that does not include the violating code.

    According to the information provided by your SDK provider, you may consider upgrading to 2.2.7-2. Please consult the SDK provider for further information.

    Affected Version(s):

    App Bundle:9, App Bundle:9

    About the User Data policy

    Limit the access, collection, use, and sharing of personal and sensitive user data acquired through the app to app and service functionality and policy conforming purposes reasonably expected by the user.

    Persistent device identifiers may not be linked to other personal and sensitive user data or resettable device identifiers except for the purposes of:

    • Telephony linked to a SIM identity (e.g., wifi calling linked to a carrier account), and
    • Enterprise device management apps using device owner mode.

    These uses must be prominently disclosed to users as specified in the User Data policy. Please consult this resource for alternative unique identifiers.

    App status: Rejected

    Your app has been rejected and wasn't published due to this policy issue. If you submitted an update, the previous version of your app is still available on Google Play.




    reason 3



    Issue with your app

    Your app is using the Cardinal Mobile SDK which collects persistent device identifiers, but may not be limited to Android ID and hardware IDs. Persistent device identifiers may not be linked to any other personal and sensitive user data and/or resettable device identifiers (e.g., IMEI, IMSI, SIM Serial #, etc).

    You may consider upgrading to a policy-compliant version of this SDK, if available from your SDK provider or removing the SDK. According to your SDK provider, you may consider upgrading to 2.2.7-2. Please consult the SDK provider for further information. Google is unable to endorse or recommend any third party software.

    About the User Data policy

    If an app handles personal and sensitive user data, then the app developer must limit the access, collection, use, and sharing of personal and sensitive user data acquired through the app to app and service functionality and policy conforming purposes reasonably expected by the user.

    Persistent device identifiers may not be linked to other personal and sensitive user data or resettable device identifiers except for the purposes of:

    • Telephony linked to a SIM identity (e.g., wifi calling linked to a carrier account), and
    • Enterprise device management apps using device owner mode.

    These uses must be prominently disclosed to users as specified in the User Data policy. Please consult this resource for alternative unique identifiers.

     


    what should I do? need help as soon as possible 

  7. Generic placeholder image

    Flora replied

    Hello,

    - Open /android/app/build.gradle and add these lines in dependencies.

    implementation('com.braintreepayments.api:drop-in:5.2.1'){
            exclude group: "org.jfrog.cardinalcommerce.gradle", module: "cardinalmobilesdk"
        }
    implementation("org.jfrog.cardinalcommerce.gradle:cardinalmobilesdk:2.2.7-2")

    - Make aab again and upload it to Play Store.

     

    Thanks & Regards

    - Flora
  8. Generic placeholder image

    Specter Hassan replied

    Guys any update about the issue?

     

Recent Tickets
URGENT Base URL is down... 5 months ago on October 30, 2025 12:10 AM river is not receiving ri... 1 year ago on January 29, 2025 9:03 AM Disable ask for Audio & V... 1 month ago on February 16, 2026 5:34 AM Want to Lunch App but get... 3 months ago on December 24, 2025 1:21 PM app creation help... 3 months ago on December 14, 2025 5:57 PM A lot of Errors In Androi... 4 months ago on November 18, 2025 1:00 AM The app is only in Englis... 4 months ago on November 11, 2025 12:28 PM problem with update files... 5 months ago on October 14, 2025 5:45 AM problems with flutter_goo... 5 months ago on October 14, 2025 5:23 AM Issues with installation... 6 months ago on September 12, 2025 10:37 AM