expo: Android app rejected because of Segment version

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

Thanks

thanks @npdbilal this is much appreciated. i will go ahead and backport the fix to sdk 44 now

@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 - it is deployed for sdk 44 now. Please run expo install expo-analytics-segment in your project to install this new version. After updating the version, bump your app version, rebuild, and resubmit.

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

@brentvatne Hey sir SDK 43

Expo-analytics-segments 11.0.4 also working perfectly…

what if i dont use the expo-analytics-segment library? should i still run expo install expo-analytics-segment anyway in sdk 43 classic build?

@corradodiba - rebuild and resubmit. classic builds (expo build), unlike EAS Build, include all modules when you build, which is part of why we are moving away from it. more context in this blog post: https://blog.expo.dev/expo-managed-workflow-in-2021-5b887bbf7dbb

it should not be necessary to update old builds but you should contact google play support if you have any further concerns, we aren’t privy to the nuance of how they handle this policy

what if i dont use the expo-analytics-segment library? should i still run expo install expo-analytics-segment anyway in sdk 43 classic build?

you do not need to install it, no. the reason you would have seen this warning bfore is that if you use classic builds (to be sunset at the end of the year, expo build:android) then it will include the entire expo sdk in the run time (https://blog.expo.dev/expo-managed-workflow-in-2021-5b887bbf7dbb). so just do a new build now and it should be fine.

@davidcort - if you share your project privately with me on github i can look into it further but your problem isn’t actionable without a reproducible example

Dear sir i confirmed that it is fixed for SDK 44

THANK YOU SO MUCH FOR YOUR COOPERATION 🙏🙏

I use SDK 44, I have not installed expo-analytics-segment in my project, yet I get the same error. What should I do?

  expo-env-info 1.0.3 environment info:
    System:
      OS: macOS 12.4
      Shell: 5.8.1 - /bin/zsh
    Binaries:
      Node: 14.17.6 - /var/folders/tg/fqh7yp0573s2c9721_wlrqtm0000gr/T/yarn--1655329815791-0.8517847943273493/node
      Yarn: 1.22.5 - /var/folders/tg/fqh7yp0573s2c9721_wlrqtm0000gr/T/yarn--1655329815791-0.8517847943273493/yarn
      npm: 6.14.15 - ~/.nvm/versions/node/v14.17.6/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.4, iOS 15.4, macOS 12.3, tvOS 15.4, watchOS 8.5
      Android SDK:
        API Levels: 23, 28, 29, 30
        Build Tools: 28.0.3, 29.0.2
        System Images: android-25 | Google Play Intel x86 Atom, android-29 | Google Play Intel x86 Atom
    IDEs:
      Android Studio: 2020.3 AI-203.7717.56.2031.7583922
      Xcode: 13.3/13E113 - /usr/bin/xcodebuild
    npmPackages:
      expo: ~44.0.0 => 44.0.6 
      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 
    npmGlobalPackages:
      eas-cli: 0.52.0
      expo-cli: 5.4.3
    Expo Workflow: managed

  "dependencies": {
    "@expo/vector-icons": "^12.0.0",
    "@react-native-async-storage/async-storage": "~1.15.0",
    "@react-native-community/netinfo": "7.1.3",
    "@react-navigation/bottom-tabs": "^6.0.5",
    "@react-navigation/native": "^6.0.2",
    "@react-navigation/native-stack": "^6.1.0",
    "@reduxjs/toolkit": "^1.7.2",
    "axios": "^0.25.0",
    "dayjs": "^1.10.7",
    "expo": "~44.0.0",
    "expo-apple-authentication": "~4.1.0",
    "expo-asset": "~8.4.4",
    "expo-av": "~10.2.0",
    "expo-blur": "~11.0.0",
    "expo-clipboard": "~2.1.0",
    "expo-constants": "~13.0.0",
    "expo-crypto": "~10.1.1",
    "expo-firebase-recaptcha": "~2.1.0",
    "expo-font": "~10.0.4",
    "expo-google-sign-in": "~10.1.0",
    "expo-linear-gradient": "~11.0.3",
    "expo-linking": "~3.0.0",
    "expo-notifications": "^0.14.1",
    "expo-splash-screen": "~0.14.0",
    "expo-status-bar": "~1.2.0",
    "expo-updates": "~0.11.7",
    "expo-web-browser": "~10.1.0",
    "firebase": "^9.6.9",
    "lottie-react-native": "5.0.1",
    "react": "17.0.1",
    "react-content-loader": "^6.1.0",
    "react-dom": "17.0.1",
    "react-native": "0.64.3",
    "react-native-dotenv": "^3.3.1",
    "react-native-elements": "^3.4.2",
    "react-native-image-viewing": "^0.2.1",
    "react-native-maps": "0.29.4",
    "react-native-safe-area-context": "3.3.2",
    "react-native-screens": "~3.10.1",
    "react-native-svg": "^12.1.1",
    "react-native-web": "0.17.1",
    "react-native-webview": "11.15.0",
    "react-redux": "^7.2.6",
    "redux-persist": "^6.0.0"
  },
  "devDependencies": {
    "@babel/core": "^7.12.9",
    "@commitlint/cli": "^16.1.0",
    "@commitlint/config-conventional": "^16.0.0",
    "@react-native-community/eslint-config": "^3.0.0",
    "@types/react": "~17.0.21",
    "@types/react-native": "~0.64.12",
    "eslint": "^7.32.0",
    "eslint-config-react-exhaustive": "1.0.1",
    "eslint-plugin-prettier": "3.4.0",
    "eslint-plugin-react-native": "^4.0.0",
    "husky": "^7.0.4",
    "react-native-svg-transformer": "^1.0.0",
    "typescript": "~4.3.5"
  },

@davidcort - can you dm me on the expo discord? this is pretty off topic with this thread because i’m fairly certain your issue is unrelated to expo-segment-analytics

Expo Workflow: bare

@davidcort - you have an android directory in your project though. this is clear because there is no prebuild phase on eas build. run npx expo-env-info in your project and share the output