App.json version doesn't seem to update

When I do a native build the app version does not update on the on the build. It’s almost like it’s stuck at my previous release. You can see in the picture my app.json has a version of 2.0.9 but when it uploads to the Expo build servers the manifest shows 2.0.7. Without incrementing that Apple rejects the new binary from test flight. Some of the things I’ve tried include:

  • Change the version and build numbers multiple times
  • Uninstall reinstall expo
  • Login/Logout
  • Try it on different machines
  • Change some of the text on the permission (they don’t seem to update)
  • Deleting the app.json (with the 2.0.9) to see if the expo-cli actually is reading it. It errors out if you do so it appears to be reading it.

Anyway it almost feels like the old app.json is being cached on the expo servers or something. Nothing I do seems to update the manifest showing up during a build.

Any thoughts?

Expo CLI 3.11.9 environment info:
System:
OS: macOS 10.14.6
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 10.16.3 - ~/.nvm/versions/node/v10.16.3/bin/node
Yarn: 1.17.3 - ~/.yarn/bin/yarn
npm: 6.9.0 - ~/.nvm/versions/node/v10.16.3/bin/npm
IDEs:
Android Studio: 3.4 AI-183.6156.11.34.5692245
Xcode: 10.3/10G8 - /usr/bin/xcodebuild
npmPackages:
@types/react: ^16.8.23 => 16.9.2
@types/react-native: ^0.57.65 => 0.57.65
expo: ^35.0.0 => 35.0.0
react: 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-navigation: ^4.0.7 => 4.0.7
npmGlobalPackages:

What exact commands are you using to run those builds?

It might be caused by --no-publish flag and building and publishing to different release channels.

I am using the --no-publish command. That makes sense that I can’t seem to update the config. I’m sure that is the issue. Thanks so much!

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