Expo CLI 3.27.13 environment info: System: OS: macOS 10.15.6 Shell: 5.7.1 - /bin/zsh Binaries: Node: 12.18.4 - /usr/local/bin/node Yarn: 1.22.5 - /usr/local/bin/yarn npm: 6.14.6 - /usr/local/bin/npm Managers: CocoaPods: 1.9.3 - /usr/local/bin/pod SDKs: iOS SDK: Platforms: iOS 14.0, DriverKit 19.0, macOS 10.15, tvOS 14.0, watchOS 7.0 Android SDK: API Levels: 28 Build Tools: 28.0.3 IDEs: Android Studio: 3.5 AI-191.8026.42.35.6010548 Xcode: 12.0.1/12A7300 - /usr/bin/xcodebuild npmPackages: expo: ~39.0.2 => 39.0.3 react: 16.13.1 => 16.13.1 react-dom: 16.13.1 => 16.13.1 react-native: ~0.63.3 => 0.63.3 react-native-web: ~0.13.12 => 0.13.14 npmGlobalPackages: expo-cli: 3.27.13 Expo Workflow: bare
I’ve been getting some strange results. When my app was smaller, the
--target bare build would run in both Expo and downloaded from Test Flight. But now as the project has grown it only runs in Expo using
--target managed and the iOS Simulator.
Every iOS bare build I upload to Test Flight just does not get passed the splash screen on a physical device and there is no errors to be seen. I have also disabled the splash screen to see if there are errors hidden behind it and still nothing. As well, I’ve tried stripping all business logic completely and just rendering a basic view and that doesn’t work either which makes me think theres some issue with the CocoaPods or some such.
(Android not being tested at this time)
Any idea what I can do?