eas submit not using the updated CFBundleShortVersionString from app.json

[DanielSepulveda]

Build/Submit details page URL

https://expo.dev/accounts/viporg/projects/vipass/submissions/1b1951a5-370a-4480-b522-57b8930fdede

Summary

When trying to submit a new iOS app store submission, EAS keeps throwing an error saying that the CFBundleShortVersionString must contain a higher version the the previously approved, even though I have already increased it.

Note

When executing expo prebuild --platform ios locally, I can see in the info.plist file that the CFBundleShortVersionString has the correct updated value.

Managed or bare?

managed

Environment

npx expo-env-info

expo-env-info 1.2.0 environment info:
    System:
      OS: macOS 14.0
      Shell: 5.9 - /bin/zsh
    Binaries:
      Node: 18.18.0 - ~/Library/Caches/fnm_multishells/17805_1709327818359/bin/node
      Yarn: 1.22.19 - ~/Library/Caches/fnm_multishells/17805_1709327818359/bin/yarn
      npm: 9.8.1 - ~/Library/Caches/fnm_multishells/17805_1709327818359/bin/npm
      Watchman: 2023.09.04.00 - /opt/homebrew/bin/watchman
    Managers:
      CocoaPods: 1.12.1 - /opt/homebrew/bin/pod
    SDKs:
      iOS SDK:
        Platforms: DriverKit 23.4, iOS 17.4, macOS 14.4, tvOS 17.4, visionOS 1.1, watchOS 10.4
    IDEs:
      Android Studio: 2022.3 AI-223.8836.35.2231.10811636
      Xcode: 15.3/15E204a - /usr/bin/xcodebuild
    npmPackages:
      expo: ^49.0.22 => 49.0.22
      react: 18.2.0 => 18.2.0
      react-dom: ^18.2.0 => 18.2.0
      react-native: 0.72.10 => 0.72.10
      react-native-web: ~0.19.6 => 0.19.10
    Expo Workflow: managed

npx expo-doctor

✔ Check Expo config for common issues
✔ Check package.json for common issues
✔ Check native tooling versions
✔ Check dependencies for packages that should not be installed directly
✔ Check for common project setup issues
✔ Check for issues with metro config
✔ Check npm/ yarn versions
✔ Check Expo config (app.json/ app.config.js) schema
✔ Check that packages match versions required by installed Expo SDK
✔ Check for legacy global CLI installed locally
✔ Check that native modules do not use incompatible support packages
✔ Check that native modules use compatible support package versions for installed Expo SDK

Didn't find any issues with the project!

Error output

No response

Reproducible demo or steps to reproduce from a blank project

eas build --profile production --platform ios --clear-cache --non-interactive --auto-submit

[szdziedzic]

Hi, I think this should help #2270 (comment)

[github-actions]

This issue is stale because it has been open for 30 days with no activity. If there is no activity in the next 7 days, the issue will be closed.

[github-actions]

This issue was closed because it has been inactive for 7 days since being marked as stale. Please open a new issue if you believe you are encountering a related problem.