eas-cli icon indicating copy to clipboard operation
eas-cli copied to clipboard

eas metadata:pull not working: Store configuration download encountered 6 errors

Open ludwighen opened this issue 1 year ago • 4 comments

Build/Submit details page URL

No response

Summary

eas metadata:pull is not working for my app. The app is published on the store, when I try to pull the metadata, I get this error message:

Store configuration download encountered 6 errors.

Could not resolve a live or editable app version

Could not resolve the editable app info to update

App version information is not prepared, can't update age rating

App version not initialized, can't download store review details

App version not initialized, can't download version

App info not initialized, can't download info

Any ideas if there is something on my end in the App Store connect configuration or if it's a bug in eas metadata?

Managed or bare?

managed

Environment

expo-env-info 1.2.0 environment info: System: OS: macOS 14.2.1 Shell: 5.9 - /bin/zsh Binaries: Node: 18.16.0 - /usr/local/bin/node Yarn: 1.22.19 - /usr/local/bin/yarn npm: 9.5.1 - /usr/local/bin/npm Managers: CocoaPods: 1.11.3 - /usr/local/bin/pod SDKs: iOS SDK: Platforms: DriverKit 23.2, iOS 17.2, macOS 14.2, tvOS 17.2, visionOS 1.0, watchOS 10.2 IDEs: Android Studio: 2023.1 AI-231.9392.1.2311.11330709 Xcode: 15.2/15C500b - /usr/bin/xcodebuild npmPackages: expo: ^50.0.11 => 50.0.11 react: 18.2.0 => 18.2.0 react-dom: 18.2.0 => 18.2.0 react-native: 0.73.4 => 0.73.4 react-native-web: ~0.19.6 => 0.19.9 npmGlobalPackages: eas-cli: 7.4.0 expo-cli: 6.3.7 Expo Workflow: bare

✔ 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

Error output

No response

Reproducible demo or steps to reproduce from a blank project

ludwighen avatar Mar 16 '24 14:03 ludwighen

@byCedric do you have any ideas?

szdziedzic avatar Apr 09 '24 09:04 szdziedzic

I am having the same issue when trying to pull metadata from an app for which the latest version was live in the store (Ready for Distribution status).

A workaround that did the trick for me was creating a new version (Prepare for Submission status) of that app in App Store Connect. Once I did that, the pull command worked.

GertSallaerts avatar May 03 '24 07:05 GertSallaerts

Having the same issue here.

$ eas metadata:pull --profile=sbmt-profile-production

EAS Metadata is in beta and subject to breaking changes.
✔ Do you want to overwrite the existing "store.config.json"? … yes

› Log in to your Apple Developer account to continue
✔ Apple ID: … [email protected]
› Restoring session /Users/greg/.app-store/auth/[email protected]/cookie
› Team Greg Fenton (*********)
› Provider Greg Fenton (**********)
✔ Logged in Local session

Downloading App Store config...

Store configuration download encountered 6 errors.

Could not resolve a live or editable app version

Could not resolve the editable app info to update

App version information is not prepared, can't update age rating

App version not initialized, can't download store review details

App version not initialized, can't download version

App info not initialized, can't download info

Check the logs for any configuration issues.
If this issue persists, open a new issue at:
https://github.com/expo/eas-cli

I don't see any "logs". Is there a command line flag to get logs? Not seeing any with --help

gregfenton avatar Oct 09 '24 08:10 gregfenton

This issue happens when you don't have an editable version in ASC

The fix is to create a new version in ASC that's editable (not been approved)

I found out because I got the same error trying to do the same thing with fastlane (but deliver has a --use_live_version=true option whereas eas does not)

louy avatar Oct 20 '25 16:10 louy