EAS Build (managed workflow) - "required a higher minimum deployment target"

Expo Development Tools
1

I found that EAS build fails if the app depends on “expo-device.” After removing it from the dependencies, it succeeded.

I know managed workflow is not fully supported, but I’ll post this if you find it useful.

Auto-linking React Native modules for target `AppName`: RNCAsyncStorage, RNCMaskedView, RNCPicker, RNGestureHandler, RNReanimated, RNScreens, react-native-safe-area-context, and react-native-viewpager
Wed, 27 Jan 2021 08:40:31 GMT
Analyzing dependencies
Wed, 27 Jan 2021 08:40:31 GMT
Fetching podspec for `DoubleConversion` from `../node_modules/react-native/third-party-podspecs/DoubleConversion.podspec`
Wed, 27 Jan 2021 08:40:31 GMT
Fetching podspec for `Folly` from `../node_modules/react-native/third-party-podspecs/Folly.podspec`
Wed, 27 Jan 2021 08:40:31 GMT
Fetching podspec for `glog` from `../node_modules/react-native/third-party-podspecs/glog.podspec`
Wed, 27 Jan 2021 08:40:31 GMT
[!] CocoaPods could not find compatible versions for pod "EXDevice":
Wed, 27 Jan 2021 08:40:31 GMT
  In Podfile:
Wed, 27 Jan 2021 08:40:31 GMT
    EXDevice (from `../node_modules/expo-device/ios`)
Wed, 27 Jan 2021 08:40:31 GMT
Wed, 27 Jan 2021 08:40:31 GMT
Specs satisfying the `EXDevice (from `../node_modules/expo-device/ios`)` dependency were found, but they required a higher minimum deployment target.

Auto-linking React Native modules for target `AppName`: RNCAsyncStorage, RNCMaskedView, RNCPicker, RNGestureHandler, RNReanimated, RNScreens, react-native-safe-area-context, and react-native-viewpager
Wed, 27 Jan 2021 08:40:31 GMT
Analyzing dependencies
Wed, 27 Jan 2021 08:40:31 GMT
Fetching podspec for `DoubleConversion` from `../node_modules/react-native/third-party-podspecs/DoubleConversion.podspec`
Wed, 27 Jan 2021 08:40:31 GMT
Fetching podspec for `Folly` from `../node_modules/react-native/third-party-podspecs/Folly.podspec`
Wed, 27 Jan 2021 08:40:31 GMT
Fetching podspec for `glog` from `../node_modules/react-native/third-party-podspecs/glog.podspec`
Wed, 27 Jan 2021 08:40:31 GMT
[!] CocoaPods could not find compatible versions for pod "EXDevice":
Wed, 27 Jan 2021 08:40:31 GMT
  In Podfile:
Wed, 27 Jan 2021 08:40:31 GMT
    EXDevice (from `../node_modules/expo-device/ios`)
Wed, 27 Jan 2021 08:40:31 GMT
Wed, 27 Jan 2021 08:40:31 GMT
Specs satisfying the `EXDevice (from `../node_modules/expo-device/ios`)` dependency were found, but they required a higher minimum deployment target.

expo diagnostics

  Expo CLI 4.1.3 environment info:
    System:
      OS: Linux 5.4 Ubuntu 20.04.1 LTS (Focal Fossa)
      Shell: 5.0.17 - /bin/bash
    Binaries:
      Node: 12.18.3 - ~/.nodebrew/current/bin/node
      Yarn: 1.22.4 - ~/.yarn/bin/yarn
      npm: 6.14.10 - ~/.nodebrew/current/bin/npm
    npmPackages:
      expo: ^40.0.0 => 40.0.1
      react: 17.0.1 => 17.0.1
      react-dom: 17.0.1 => 17.0.1
      react-native: https://github.com/expo/react-native/archive/sdk-40.0.1.tar.gz => 0.63.2
      react-native-web: ~0.13.12 => 0.13.18
    npmGlobalPackages:
      expo-cli: 4.1.3
    Expo Workflow: managed
2

hi there! what version of expo-device do you have installed? the latest version that we published from master depends on ios 11+, but expo-device@2.4.0 (which is the version supported in sdk 40) supports ios 10+. i suspect you installed a version that is incompatible with managed workflow currently in your app (anything > 2.4.0). expo install expo-device should fix it in your project

1 Like
3

@notbrent I use expo-device 2.4.0 but noticed that sentry-expo@3.0.4 depends on expo-device@3.1.1. After upgrading sentry-expo to 3.0.5 that depends on expo-device@2.4.0, the build succeeded! Thanks a lot!

1 Like
4

This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.