-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(Google Play Warning) Sending Device Identifiers #106
Comments
Hi @felipeaugusto1 thank you for bringing this to our attention. We recently made changes to how advertising ids are handled in Android. I will check with the team to see if these issues are being addressed in that update. |
Great to hear that @justin-fiedler . Thanks for the quick reply |
@felipeaugusto1 can you please provide the version the SDK you are using? |
@justin-fiedler I'm using 2.6.0 |
@felipeaugusto1 In android SDK, did you import the library for advertising id? We only fetch adversing id when the certain library is imported. |
@qingzhuozhen what android SDK are you referring to? |
@felipeaugusto1 underlying ReactNative SDK is using our Android SDK now. To get advertising id, you need to install package like |
@qingzhuozhen Ah I see. I do have that package in my gradle file |
Sending Device Identifiers
Your app is using device identifiers (IMEI, MAC address, Build Serial, etc.) and sending identifier data to a remote network address.
This issue is commonly (but not only) found in apps using an outdated Advertising SDK.
Our analysis suggests that for your APK, this behavior is caused by the Advertising SDK(s) 'com.amplitude.api' although there may be additional SDKs or source code contributing to it. To stop receiving this warning, try updating or changing this (these) SDK(s) and check any other SDKs or code that may be using device identifiers.
Sending device identifiers is not a best practice for most use-cases and if you're using this identifier for advertising purposes, this may be a violation of Google Play policies and can affect your app's visibility on the Play Store.
The text was updated successfully, but these errors were encountered: