expo: "No launchable updates found in database" when loading unsupported SDK in development in Expo client
🐛 Bug Report
Summary of Issue
Receiving message “No launchable updates found in database” when attempting to run app on iphone 11 simulator.
Environment - output of expo diagnostics & the platform(s) you’re targeting
Expo CLI 3.27.8 environment info:
System:
OS: macOS Mojave 10.14.6
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 12.18.4 - /usr/local/bin/node
Yarn: 1.16.0 - /usr/local/bin/yarn
npm: 6.14.6 - /usr/local/bin/npm
Managers:
CocoaPods: 1.8.4 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: iOS 13.2, DriverKit 19.0, macOS 10.15, tvOS 13.2, watchOS 6.1
IDEs:
Xcode: 11.2/11B52 - /usr/bin/xcodebuild
npmPackages:
expo: ^35.0.0 => 35.0.1
react: 16.8.3 => 16.8.3
react-dom: 16.8.3 => 16.8.3
react-native: https://github.com/expo/react-native/archive/sdk-35.0.0.tar.gz => 0.59.8
react-native-web: ^0.11.7 => 0.11.7
react-navigation: ^4.1.1 => 4.1.1
npmGlobalPackages:
expo-cli: 3.27.8
Expo Workflow: managed
Reproducible Demo
Steps to Reproduce
- Deploy app via
expo publishcommand - Attempt to run app locally in IOS iphone 11 simulator via
yarn startcommand - App does not load and displays message “No launchable updates found in database” on the iphone simulator
Expected Behavior vs Actual Behavior
Expected Behavior: Be able to run the app locally on iphone simulator without receiving the message “No launchable updates found in database”. Actual Behaviour: App does not open on simulator and displays message “No launchable updates found in database”
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 16 (10 by maintainers)
Thanks! Updating the SDK to 39.0.0 worked.
Getting error
Warning: Function components cannot be given refs. Attempts to access this ref will fail. Did you mean to use React.forwardRef()"after updating, but this is a separate issue that I’ll need to look into.@JChristensen97 - oh sorry, i missed that you are using sdk 35, so this is the same issue as @leslielyj is facing. it’s not supported in the latest expo client. see: https://blog.expo.io/expo-sdk-39-is-now-available-4c10aa825e3f - we dropped sdk 35 in this release.
@leslielyj - the latest expo client does not support sdk 35.