Solution 1 :
Just happened to me too, possibly it will be solved if we try to generate the bundle using the EAS command.
Then change this command:
expo build:android
by this command:
eas build -p android
Then the bundle will be cleaner because it will bring only what it needs. Another alternative might be to update the version of one of the possible packages involved such as “expo-firebase-analytics” or “expo-ads-admob”. In my case I currently have:
"expo-ads-admob":"~12.0.0", "firebase": "8.2.3", "expo-firebase-analytics":"~6.0.0".
I have not updated it yet
pd: remember that in future versions of expo I understand that the command will stop working:
expo build:android
Solution 2 :
The issue is with expo-analytics-segment.
api 'com.segment.analytics.android:analytics:4.9.4'
But this is only removed if you use EAS.
Solution 3 :
This is resolved in expo-analytics-segment
11.2.1 – https://github.com/expo/expo/issues/17845. You can update with:
expo install expo-analytics-segment
Problem :
I am trying to submit my React Native EXPO app to Google Play Store for approval, but I am getting this error:
SDK Segment Analytics Android (com.segment.analytics.android:analytics), 4.9.4 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.
You can’t publish this release due to this policy issue. To be allowed to publish, 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.
I am new to React Native. Please Help.
Comments
Comment posted by github.com/expo/expo/issues/17845
github.com/expo/expo/issues/17845
Comment posted by Andrew Jang
Did this work? I used
Comment posted by Andrew Jang
I don’t use expo-analytics-segment & I already use