Your app includes non-compliant SDK version

[ovalwmaniero]

Report

Hi, We are getting this error from Google Play Console as soon as we upload the APK

Your app includes non-compliant SDK version Your app includes SDK com.segment.analytics.android:analytics or an SDK that one of your libraries depends on, 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. Starting from 12 August 2022 midnight (UTC), new app releases containing the SDK version(s) that do not comply with the User Data policy may 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 4.10.1. Please consult the SDK provider for further information. ACTION REQUIRED: Upload a new compliant version AND deactivate the noncompliant version.

Since we are not using the above mentioned package anywhere, I found out after some digging that appsflyer uses com.segment.analytics.android.

Can you please confirm that? and if yes, can you please try to fix the error?

Thanks in advance

Plugin Version

react-native-appsflyer 6.1.30

On what Platform are you having the issue?

android

What did you do?

Just build the apk and upload it to the Google Play Console

What did you expect to happen?

Upload success without error

What happened instead?

A warning is raised and shortly will become a blocker

[amit-kremer93]

Hii @ovalwmaniero can you please point to the place where the sdk uses this dependency?

[ovalwmaniero]

Hi @amit-kremer93,

Im not sure where is being used but from my digging process I found out that the only lib that uses com.segment.analytics.android is AppsFlyer.

I disassembled my compiled .dex

and the only line that uses that SDK in my whole project compiled .dex is the one you see in the screenshot above.

[github-actions[bot]]

👋 Hi @ovalwmaniero and Thank you for reaching out to us. In order for us to provide optimal support, please submit a ticket to our support team at [email protected]. When submitting the ticket, please specify:

• ✅ your AppsFlyer sign-up (account) email
• ✅ app ID
• ✅ production steps
• ✅ logs
• ✅ code snippets
• ✅ and any additional relevant information.

[amit-kremer93]

@ovalwmaniero in our RN plugin we don't use segment. did you install this plugin also?

[ovalwmaniero]

@amit-kremer93 we don't use the segment plugin, maybe the segment dependency is getting included in the final SDK as a transitive dependency?

I guess that the Google Play console is only searching for a reference to the segment dependency and as soon as is found, the error is triggered, even if the library is not getting used.

[pedpess]

Hi all, I think I have the same issue with this, checking my .dex file for the APK it also shows this package. Any resolution at this point in time like a new release with this package removed/updated?

[amit-kremer93]

It looks like it is related to our native android sdk so we will keep you updated. Thank you.

[pedpess]

Hi @amit-kremer93 just to update you that Google nicely increased their deadline to fix this from the 28th of August to -> 24th of September. 😄

Would you have at this stage a forecast of when this update would land so we can update it?

[leolusoli]

Hi @amit-kremer93 hope you well. We're near to the block data for Google Play Store. Can you give us am estimated date when this will be fixed (if will be fixed)? Otherwise, we'll be obligated to remove the SDK from our app in order to continue to release out our application.

cc @ovalwmaniero

[pedpess]

@leolusoli Appsflyer team recently released a new version of the RN containing the updated Android SDK :). Just update. Cheers!

[leolusoli]

@pedpess Very nice news :) Thank you so much... Do you know if there's a changelog for review the other changes in addition to this one?

[pedpess]

@leolusoli there's but they don't write anything. I found out the SDK got updated because I saw the new version of the RN lib and I saw the diff comparing with the previous version

[guysarfatty-af]

@leolusoli @pedpess Thanks for your feedback! We are working on a fix that will mitigate this issue, by removing the line that was referenced in the Google Play warning. I would like to emphasise that the line was used by the SDK to determine the type of plugin that is running the SDK, and by no means was it loading any additional library to be used inside the RN plugin. Now this line has been removed from the code and the problem should be resolved. We will issue a new version of the React Native plugin later this week as version 6.9.1. Thanks!

[leolusoli]

So @guysarfatty-af, @pedpess is not right to say that in the last current version (at the moment of writing: 6.8.2) the issue is not resolved. Right?

[pedpess]

Thanks @guysarfatty-af , I noticed this today when our app came back with the warning message again from Google 😅, so the changes posted in the SDK were not enough to fix the issue. I will continuing following here as well as update the lib as soon as it's released

[leolusoli]

Ok, no worries :) Thank you @pedpess

[leolusoli]

@guysarfatty-af News about that? The deadline is near.

[pedpess]

@leolusoli the version promised with the fix 6.9.1 was released 5 days ago, just update it and submit it to Google Play. 🤞🏻

[zirgulis]

Does anyone still getting warnings in regards to this? We have updated the react-native-appsflyer to 6.9.2 but google store support team says our latest app bundle is still not compliant. Would appreciate any inputs on this 🙏

[pedpess]

@zirgulis I would keep in 6.9.1 for now, but your version should have the update in theory. I stopped getting the complains after updating. Maybe you could try to update to the latest 6.9.4? Check their Android repo where you can see what was changed in the SDK, might help!

[sregg]

We also received this email from Google today saying our app update was rejected because the AppsFlyer SDK was collecting some data:

Issue details

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

Version code 479: 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), Possible SDKs: com.appsflyer:af-android-sdk
Version code 645: 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), Possible SDKs: com.appsflyer:af-android-sdk, com.google.android.gms:play-services-measurement-impl
To bring your app into compliance, follow these steps:

com.appsflyer:af-android-sdk com.appsflyer:af-android-sdk: Consider upgrading to a policy-compliant version of the SDK if available from your SDK provider, or removing the SDK.
com.google.android.gms:play-services-measurement-impl com.google.android.gms:play-services-measurement-impl: Consider upgrading to a policy-compliant version of the SDK if available from your SDK provider, or removing the SDK.

Did anyone receive this? How did you fix it?

[phanhungphong0406]

We also received this email from Google today saying our app update was rejected because the AppsFlyer SDK was collecting some data:

``` Issue details

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

Version code 479: 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), Possible SDKs: com.appsflyer:af-android-sdk Version code 645: 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), Possible SDKs: com.appsflyer:af-android-sdk, com.google.android.gms:play-services-measurement-impl To bring your app into compliance, follow these steps:

com.appsflyer:af-android-sdk com.appsflyer:af-android-sdk: Consider upgrading to a policy-compliant version of the SDK if available from your SDK provider, or removing the SDK. com.google.android.gms:play-services-measurement-impl com.google.android.gms:play-services-measurement-impl: Consider upgrading to a policy-compliant version of the SDK if available from your SDK provider, or removing the SDK.

Did anyone receive this? How did you fix it?

Me too, can you solve it? Please help me

[sregg]

For now I changed our Data Safety form and checked the Device ID checkbox.

[aouuthanapat]

For now I changed our Data Safety form and checked the Device ID checkbox.

Is that working?

[sregg]

For now I changed our Data Safety form and checked the Device ID checkbox.

Is that working?

Yeah Google approved the app after that. But ideally the AppsFlyer SDK doesn't collect the device ID.