fastlane build_app does not apply Flutter Flavor / Xcode Scheme
#21924
Comments
Update:Now I have learned that the app flavor is not necessarily equivalent to the Xcode app scheme. When I set the configuration and scheme in the |
|
It seems like your Fastlane configuration is not recognizing the specified scheme ("staging") during the build process, resulting in a fallback to the default "Release" scheme. This can be frustrating, especially when everything works fine locally but fails in the CI/CD pipeline. Here are a few steps you can take to troubleshoot and potentially resolve this issue:
By following these steps and carefully analyzing the Fastlane output, you should be able to diagnose and resolve the issue with specifying the scheme during the build process in your CI/CD pipeline. If the problem persists, you might need to provide more detailed logs or seek assistance from the Fastlane community for further troubleshooting. |
|
Thank you for your advice, but as I already indicated in my previous comment, I tried to achieve something that is not possible with the For now, I built a workaround to determine in which environment the app currently is. The Flutter Plugin Since this is no issue directly associated with fastlane, we can close this issue. |
New Issue Checklist
Issue Description
We are currently using Fastlane with GitHub Actions as CI/CD pipeline for our Flutter Project. We have the issue that we want to build the app with different flavours/schemes depending on the target environment (TestFlight/Android Internal Test Track for Testing, App Store, Play Store Prod for Production) but the specified flavor/scheme seems to get lost during the
build_appcommand. This results in performing a "fallback" to the default "Release" scheme, resulting in the app having no flavor (CallingappFlavorin the Flutter App returnsnull). But when running/building the app locally without fastlane, everything works fine and the flavor/scheme is applied correctly. Please don't mind theappStore_prodlane, it is only preserved for the future. For now, only theappStore_testlane is important. I hope you are able to help me.Command executed
Complete output when running fastlane, including the stack trace and command used
Environment
Verification that the desired scheme exists in the GitHub runner(Output of
xcodebuild -list):Command line invocation: /Applications/Xcode_15.0.1.app/Contents/Developer/usr/bin/xcodebuild -list User defaults from command line: IDEPackageSupportUseBuiltinSCM = YES Information about project "Runner": Targets: Runner RunnerTests Build Configurations: Debug Debug-production Debug-staging Debug-development Release Release-production Release-staging Release-development Profile Profile-production Profile-staging Profile-development If no build configuration is specified and -scheme is not passed then "Release" is used. Schemes: development production Runner stagingThe text was updated successfully, but these errors were encountered: