I am currently using a managed React Native workflow, created by the EAS CLI.
My eas-cli version is eas-cli/0.40.0 darwin-x64 node-v14.17.3
The issue is that every time I ran EAS submit to the app store, specifically to TestFlight,
Command line: eas submit -p ios --latest --profile dev
I get this error: Couldn't find any builds for this project on EAS servers. It looks like you haven't run 'eas build' yet.
Of course, I’ve built my application first before running this command to ensure I have the proper working build. I can use the build ID, but my goal is to recreate the same flow using a CI pipeline. Has anyone came across this error before?
Hmm I am using the app.json, but I’m not updating the slug. And yes, I am currently running the eas submit on the same computer using the same account.
For some reason, it just started working now. But now that I think about it, we will most likely stick to using a specific build ID to submit due to the fact that we’ll be potentially using the EAS CLI for multiple applications within the same organization. So not to use with --latest, which could conflict with different app’s builds. Please let me know if there’s a better way.
you can build with --auto-submit option, if you run that on ci together with --no-wait option cli command will exit after build start, so your ci does no need too run idly while waiting for the build to finish
if you don’t want to submit automatically, you can run build with --json option parse stdout with e.g. jq and use id extracted from json to run submit command