I’m making an attempt 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 operating 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 atmosphere |
+---------------+-------------------------+
| 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 making an attempt now for a number of days random options from a wide range of points on GitHub with none of them working I’m questioning if there’s a structured approach to drill down and debug the problem.
When inspecting the log or operating the command manually there are lots of be aware: and warning log strains however no error / failure or some other telling message.
Not having used xcodebuild up to now I’m questioning if there’s any choice to extend the verbosity (aside from -verbose – which didn’t assist) or someway dissect this drawback to seek out the foundation trigger (and if by any likelihood somebody is aware of the answer this may be much more superior 😀).
