Android app rejected because of Segment version

[brentvatne]

On Friday, June 10, 2022, we began to receive reports that apps submitted to the Google Play Store were in some cases being rejected due to the inclusion of com.segment.analytics.android:analytics 4.9.4. This impacted all classic builds (expo build:android - more info on why), bare apps that use expo-analytics-segment, and EAS Build apps that use expo-analytics-segment.

See submission error message

On Monday, June 13, we deployed expo-analytics-segment version 11.2.1 to resolve the issue for SDK 45 bare apps and apps using EAS Build. We also updated classic builds for SDK 45 to include this fix. Please run expo install expo-analytics-segment (if you use the library) in your project to install this new version. After updating the version, bump your app version, rebuild, and resubmit.

We will deploy fixes to older SDK versions once affected users have confirmed that the issue has been resolved for them. Please confirm in this thread that the above instructions unblock your submission on SDK 45 apps with expo-analytics-segment.

On Wednesday, June 15, we deployed expo-analytics-segment updates for SDK 44 and SDK 43. We also update classic builds for SDK 44 and 43 to include this fix. Please run expo install expo-analytics-segment (if you use the library) in your project to install this new version. After updating the version, bump your app version, rebuild, and resubmit.

[srossidev]

We will deploy fixes to older SDK versions once affected users have confirmed that the issue has been resolved for them. Please confirm in this thread that the above instructions unblock your submission on SDK 45 apps with expo-analytics-segment.

Same issue here.
My app was rejected by Google Play Console cause SDK com.segment.analytics.android:analytics 4.9.4 is not comply with the User Data policy. Expo Env Info as follow:

System:
OS: macOS 12.3.1
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 14.13.1 - /usr/local/bin/node
Yarn: 1.22.10 - /usr/local/bin/yarn
npm: 6.14.8 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.10.1 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 21.2, iOS 15.2, macOS 12.1, tvOS 15.2, watchOS 8.3
IDEs:
Android Studio: 2020.3 AI-203.7717.56.2031.7784292
Xcode: 13.2.1/13C100 - /usr/bin/xcodebuild
npmPackages:
expo: ~43.0.2 => 43.0.5
react: 17.0.1 => 17.0.1
react-dom: 17.0.1 => 17.0.1
react-native: ^0.64.3 => 0.64.3
react-native-web: 0.17.1 => 0.17.1
react-navigation: ^4.4.4 => 4.4.4
npmGlobalPackages:
eas-cli: 0.53.1
expo-cli: 5.4.9
Expo Workflow: managed

Any suggestion about older (43) SDK versions?

[brentvatne]

@srossidev - it is already established in the original post that this will occur for some folks at the moment. I have deployed a possible fix for SDK 45. We will deploy fixes to older SDK versions once affected users have confirmed that the issue has been resolved on SDK 45.

[npdbilal]

Hi sir the new update is working for SDK 45 but i want update for SDK 44 please

Thanks

[schorzi1]

When do you think the SDK 44 update will be published?
Thanks!

[DharmeshBasapatiBacancy]

Is there any way we can build release build other than EAS way? I mean from Android Studio by getting the release keystore from expo-cli or something like that.

[JamiiTelecom]

Still experiencing this issue with my build, see snapshot of my package.json

PlayStore Notice

[npdbilal]

If the developer fix the version 11.1.0 so it will automatically fixed

[brentvatne]

Still experiencing this issue with my build, see snapshot of my package.json

PlayStore Notice

did you use EAS Build or expo build?

[npdbilal]

It is working on Expo SDK 45

But not working on Expo SDK 44

I am not using expo-analytics-segments anywhere or if i updating the expo-analytics-segments to 11.2.1 so when i build the app it is automatically changed to 11.1.0

I cannot use SDK 45 because few packages have deprecated in SDK 45 that i am using in my app.

Please help to resolve of Expo-analytics-segment @11.1.0

Please sir

And i am using Expo build , i can not move to the EAS build in current time.

[brentvatne]

@npdbilal - thank you for the information. so, to confirm very clearly:

using expo build:android, you verified that this works for you on sdk 45. however, it does not work for you on sdk 44 using expo build:android. is this correct?

[npdbilal]

Yes sir this is correct therefore i show you both version above one is SDK 45 and down one is SDK 44

there is just need to implement in build.gradle in 11.1.0