Expo CLI 4.1.6 environment info:
System:
OS: macOS 11.2.3
Shell: 5.8 - /bin/zsh
Binaries:
Node: 12.16.3 - ~/.nvm/versions/node/v12.16.3/bin/node
Yarn: 1.22.4 - ~/.nvm/versions/node/v12.16.3/bin/yarn
npm: 6.14.9 - ~/.nvm/versions/node/v12.16.3/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.9.1 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: iOS 13.7, DriverKit 19.0, macOS 10.15, tvOS 13.4, watchOS 6.2
IDEs:
Android Studio: 4.1 AI-201.8743.12.41.7042882
Xcode: 11.7/11E801a - /usr/bin/xcodebuild
npmPackages:
expo: ^40.0.0 => 40.0.1
react: 16.13.1 => 16.13.1
react-dom: 16.13.1 => 16.13.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.6
Expo Workflow: managed
EAS submit fails because of:
The bundle uses a bundle name or display name that is already taken
The thing is - indeed, the first time I did eas build
for iOS, I mistakenly had {...name: "CONNECT"...}
in my app.json. But even after I changed that to {...name: "Taranis CONNECT"...}
it still fails on the same error. it’s as if there is some kind of caching somewhere. if I use expo build:ios
and using Transporter it works. I want to use eas. please help.