EAS Build generating debug DYSM even when release is specified in build configuration

[CODERlsg]

Build/Submit details page URL

No response

Summary

Hi,

I am creating a new application and i was testing eas on managing releases and builds to app store and google play store. The application is built using expo sdk 51 and it's prebuilt app which has ios and android native folders separately in the source code. I also have some flavors specified in ios and android, natively. This is the configuration I have set for ios for production

 "production": {
      "distribution": "store",
      "credentialsSource": "remote",
      "ios": {
        "buildConfiguration": "Release",
        "scheme": "TestApp-Production"
      }
    }

However when generating it through eas (locally and cloud), I see this log in fastlane saying

› Generating debug TestApp/TestApp-Production » TestApp.app.dSYM

This is a bit confusing because I cannot inspect whether the actually generated ipa is a debug or release version.

Surprisingly I also see this log in fastlane

| scheme                | TestApp-Production                                                                                                                                |
| configuration         | Release     


$ xcodebuild -resolvePackageDependencies -workspace ./TestApp.xcworkspace -scheme TestApp-Production -configuration Release
▸ Command line invocation:
▸     /Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild -resolvePackageDependencies -workspace ./TestApp.xcworkspace -scheme TestApp-Production -configuration Release
▸ User defaults from command line:
▸     IDEPackageSupportUseBuiltinSCM = YES
▸ resolved source packages:
$ xcodebuild -showBuildSettings -workspace ./TestApp.xcworkspace -scheme TestApp-Production -configuration Release 2>&1

which i found really confused whether the output is a release or a debug.

Can i know whether this is behavior usual?

Managed or bare?

bare

Environment

Expected package @expo/config-plugins@~8.0.0
Found invalid:
  @expo/[email protected]
  @expo/[email protected]
  @expo/[email protected]
  (for more info, run: npm why @expo/config-plugins)
Expected package @expo/prebuild-config@~7.0.0
Found invalid:
  @expo/[email protected]
  (for more info, run: npm why @expo/prebuild-config)
Expected package @expo/metro-config@~0.18.11
Found invalid:
  @expo/[email protected]
  @expo/[email protected]
  (for more info, run: npm why @expo/metro-config)
Expected package metro@~0.80.8
Found invalid:
  [email protected]
  (for more info, run: npm why metro)
Expected package metro-resolver@~0.80.8
Found invalid:
  [email protected]
  [email protected]
  (for more info, run: npm why metro-resolver)
Expected package metro-config@~0.80.8
Found invalid:
  [email protected]
  (for more info, run: npm why 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:
  [email protected] - expected version: ~51.0.39
  [email protected] - expected version: ~3.5.24
  [email protected] - expected version: ~0.27.7
Your project may not work correctly until you install the expected versions of the packages.
Found outdated dependencies

Error output

No response

Reproducible demo or steps to reproduce from a blank project

For setting up flavors I followed https://www.youtube.com/watch?v=rhdOWYqc-Cg.

And as mentioned above I have set up the eas.json as well with correct scheme and configuration. I ran the below command to check it manually

eas build --platform ios -e production --local