[EAS Credentials / Submit] Old "Apple Team" used after app transfer on App Store is causing Submit errors

[giovannilondero]

Build/Submit details page URL

https://expo.dev/accounts/visup/projects/dihr/submissions/82f02be2-83bf-496a-ad26-ba0ac5099113

Summary

After transferring two apps to a new account on App Store, it seems EAS is keeping the old team id somehow, and I cannot find a proper way to change/reset it.

This is (or seems to be) causing issues with eas submit as I get "The provided entity includes a relationship with an invalid value" error.

I updated appleTeamId in eas.json, I logged out and in again, I removed ~/.app-store folder, I recreated credentials on EAS... nothing has worked so far.

Using eas credentials and proceeding with ios and production options, I still see the old team id on the summary (when function displayIosCredentials is invoked here). It seems that wrong data is pulled here, but I can't debug any further at the moment.

Managed or bare?

Managed

Environment

expo-env-info 1.2.1 environment info:
System:
OS: macOS 14.6.1
Shell: 5.9 - /bin/zsh
Binaries:
Node: 20.12.2 - ~/Library/pnpm/node
Yarn: 1.22.22 - ~/Library/pnpm/yarn
npm: 10.5.0 - ~/Library/pnpm/npm
Watchman: 2024.08.26.00 - /opt/homebrew/bin/watchman
Managers:
CocoaPods: 1.15.2 - /Users/giovannilondero/.gem/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 24.1, iOS 18.1, macOS 15.1, tvOS 18.1, visionOS 2.1, watchOS 11.1
IDEs:
Android Studio: 2024.2 AI-242.23339.11.2421.12550806
Xcode: 16.1/16B40 - /usr/bin/xcodebuild
npmPackages:
expo: ^51.0.22 => 51.0.22
expo-router: ~3.5.18 => 3.5.18
react: 18.2.0 => 18.2.0
react-dom: 18.2.0 => 18.2.0
react-native: 0.74.3 => 0.74.3
react-native-web: ~0.19.10 => 0.19.12
Expo Workflow: bare

---

✔ Check package.json for common issues
✔ Check Expo config for common issues
✔ Check for common project setup issues
✔ Check dependencies for packages that should not be installed directly
✔ Check for issues with Metro config
✔ Check npm/ yarn versions
✔ Check if the project meets version requirements for submission to app stores
✔ Check for app config fields that may not be synced in a non-CNG project
✔ Check Expo config (app.json/ app.config.js) schema
✔ Check native tooling versions
✖ 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

Detailed check results:

Expected package @expo/metro-config@~0.18.11
Found invalid:
@expo/[email protected]
(for more info, run: npm why @expo/metro-config)
Advice: Upgrade dependencies that are using the invalid package versions.

The following packages should be updated for best compatibility with the installed expo version:
@sentry/[email protected] - expected version: ~5.24.3
[email protected] - expected version: ~51.0.39
[email protected] - expected version: ~14.0.7
[email protected] - expected version: ~4.0.29
[email protected] - expected version: ~12.0.10
[email protected] - expected version: ~3.5.24
[email protected] - expected version: ~0.27.7
[email protected] - expected version: ~0.25.27
[email protected] - expected version: 0.74.5
Your project may not work correctly until you install the expected versions of the packages.
Found outdated dependencies
Advice: Use 'npx expo install --check' to review and upgrade your dependencies.

One or more checks failed, indicating possible issues with the project.

Error output

No response

Reproducible demo or steps to reproduce from a blank project

It seems quite a specific issue...

Run eas credentials, proceed by selecting ios and production until you get to the "iOS Credentials" summary of the desired app: wrong Apple Team