mParticle customers using Android SDK version 5.34.3 and earlier, or Cordova plugin version 2.1.0 and earlier, have begun receiving warnings from Google Play Console that their app includes a “non compliant SDK version” when submitting app updates. The warning indicates that future app submissions using these older SDK versions will be blocked from release at a later date, typically late June or early July 2022.
These warnings are the result of changes to the Google Play User Data policy that were announced on July 28, 2021. To support the policy changes, mParticle has updated the Android SDK so that it no longer automatically collects Android ID starting with version 5.35.0. We have also updated the Cordova plugin to utilize the updated Android SDK starting with version 2.2.0.
Upgrading the mParticle Android SDK to version 5.35.0 or newer, or Cordova plugin to version 2.2.0 or newer, is recommended for all customers and is required to comply with the updated User Data policy. You will not be able to release new app updates to the Play Store after the Google-set deadline for your app without upgrading to a new, policy-compliant version of the SDK.
Existing apps that have already been released with earlier versions of the mParticle SDK will continue to function and send data to mParticle.
Upgrading the Android SDK
You can upgrade to a newer version of the mParticle Android SDK by modifying your app’s
Always stay up-to-date with the latest minor versions released as part of major version 5:
Pin your app to the minimum compliant version:
Upgrading the Cordova Plugin
You can upgrade to newer versions of the mParticle Cordova Plugin by pulling the latest package from npm or from mParticle/cordova-plugin-mparticle on GitHub.
cordova plugin rm cordova-plugin-mparticle
cordova plugin add cordova-plugin-mparticle
Example Warning from Google Play Console
Your app includes non compliant SDK version
[version]which collects personal or sensitive data that includes but may not be limited to Advertising ID, Android ID identifiers. Persistent device identifiers may not be linked to other personal and sensitive user data or resettable device identifiers as described in the User Data policy.
[date]midnight (UTC), new app releases containing the SDK version(s) that do not comply with the User Data policy will be blocked from release. 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 5.35.0. Please consult the SDK provider for further information.
Read through the User Data policy for more details, and how to submit an updated app for review here.
If you've reviewed the policy and feel our decision may have been in error, please reach out to our policy support team.