I’m attempting to get a Flutter app to construct utilizing match and fastlane.
Match appears to work as All required keys, certificates and provisioning profiles are put in
When working build_ios_app() I get the next output:
[08:13:05]: ▸ The next construct instructions failed:
[08:13:05]: ▸ Archiving workspace Runner with scheme Runner
[08:13:05]: ▸ (1 failure)
[...]
** ARCHIVE FAILED **
The next construct instructions failed:
Archiving workspace Runner with scheme Runner
(1 failure)
[08:13:05]: Exit standing: 65
+-----------------------------------------+
| Construct setting |
+---------------+-------------------------+
| xcode_path | /Functions/Xcode.app |
| gym_version | 2.227.1 |
| export_method | app-store |
| sdk | iPhoneOS18.4.sdk |
+---------------+-------------------------+
The command that failed is the next:
/Functions/Xcode.app/Contents/Developer/usr/bin/xcodebuild -workspace ios/Runner.xcworkspace -scheme Runner -configuration Launch -destination generic/platform=iOS -archivePath "/Customers/builder/Library/Developer/Xcode/Archives/2025-04-24/Runner 2025-04-24 06.01.57.xcarchive" archive
After attempting now for a number of days random solutions from a wide range of points on GitHub with none of them working I’m questioning if there’s a structured strategy to drill down and debug the difficulty.
When inspecting the log or working the command manually there are loads of observe: and warning log strains however no error / failure or every other telling message.
Not having used xcodebuild previously I’m questioning if there may be any choice to extend the verbosity (aside from -verbose – which didn’t assist) or someway dissect this downside to search out the basis trigger (and if by any probability somebody is aware of the answer this could be much more superior 😀).