fastlane | fastlane setup to deploy iOS Apps | iOS library

There are a number of things to look into.
If you are running Expo in the SDK then no need for cocoa pods just the most up-to-date version of the CLI tool.

Run expo --version to determine what version you are currently working with. Update if needed.

Adding a profile might be useful too. Along with checking your config. Configuring EAS Build with eas.json

eas build --platform ios --profile distribution

Also, be sure that all the apple certificates are active and connected to your Expo account for that project.

I found the reason. I need to upload at least one build to google Play store app manually. That’s why I got package name error.

probably i have changed The xcode ruby, and formatting the computer solve my issue

The problem wasn't the attribute or the method, but the naming of the track.

I worked with upper and lower case, or with hyphens.

The following naming in fastlane and in Google Console works fine:

supply ( track: "alphaa", apk: "build/app/outputs/apk/release/app-release.apk" )

Ok, so I kind of fixed it.

What I did was to reinstall npm & nvm with homebrew, delete the package-lock.json and then run npm install. For some reasons, I didn't have any folders named "node_modules" and my package-lock didn't contain any lines with the module "react-native" so I added it back.

Now I'm stuck with something else but I guess I'll have to open a new ticket !

I have managed to solve this problem by creating a fastlane folder in the root folder of my react-native project and inside that I have initiated the fastlane command. Before I used to have the fastlane folder inside iOS folder.

Now the folder structure looks like this

• Root
  • android
  • ios
  • fastlane
    • Appfile
    • Fastfile
    • Gemfile
    • Gymfile

xcodebuild and xcrun help build Xcode projects in a headless context, for example in CI setups. swift is the Swift REPL and is largely used for Swift on Server apps. As such, we can build apps without knowing about or using the tools regularly in mobile app development. We use xcodebuild and xcrun under the hood interacting with Xcode even though we don't realise it because they're bundled in Xcode's Command Line tools (documentation archive, but still relevant).

fastlane is an example CI tool that automates the build process, certificate signing, and interfacing with App Store Connect, using these tools.

xcodebuild is part of Xcode's bundled command-line tools package. From the manpages:

build Xcode projects and workspaces

xcodebuild builds one or more targets contained in an Xcode project, or builds a scheme contained in an Xcode workspace or Xcode project.

xcodebuild has lots of options and use cases. The options are equivalent to certain user actions within the Xcode IDE. Example usage:

so I figured it out. If anyone has the same issue, the fix for this current problem is that you have to run a gradle task in the root directory of the project, before building the iOS part.

./gradlew generateDummyFramework

In my case with Jenkins I added sh './gradlew generateDummyFramework before the sh 'pod install' shell command in the Build stage. This fixed the issue in question.

The problem was caused from Cocoapods not being able to access the framework file, hence pod install can't configure the framework correctly. The reason for the build to fail on the first build but not on the second is because the framework file is generated when you run a build in XCode. After that Cocoapods can configure the file correctly.

If anyone has a different answer I'm eager to know about it!

I see that is_ci also ran. Does your match command look like this: match(.., readonly: is_ci, ...) and are you running the command on a CI service like Jenkins or some other one? If so, run it locally first, that will generate all the relevant certs and provisioning profiles needed. Then run it on your CI service again.