Encountered error while archiving for device.

[il2be97]

Select Topic Area

Question

Body

I'm encountering an issue with my iOS workflow.

Everything works fine when building the project locally, but the pipeline fails when running the workflow (even previously successful pipelines no longer work).

Here's the relevant output:

vbnet
Copy
Edit
Running pod install... 146.8s
Running Xcode build...
Xcode archive done. 6.4s
Failed to build iOS app
Uncategorized (Xcode): Exited with status code 1

Encountered error while archiving for device.
It seems like the Xcode archive step finishes immediately without providing any detailed error messages.

I tried adding the --verbose flag, but it didn't reveal any additional information.

Has anyone faced a similar issue or knows what might be causing this?

attached part of building logs:
8_Build iOS Ad Hoc distribution app.txt

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[Hanashiko]

Hi there,

From the build output, we can see that the pipeline fails during the Xcode archiving step, showing:

Xcode archive done. 5.6s  
Failed to build iOS app  
Uncategorized (Xcode): Exited with status code 1  
Encountered error while archiving for device.

However, this message is quite generic and doesn’t pinpoint the actual issue. Here are a few suggestions that might help you troubleshoot further:

---

1. Enable Full Xcode Build Output

You mentioned using --verbose, but for Xcode, that may not show everything. Try running with:

xcodebuild -workspace YourApp.xcworkspace \
           -scheme YourApp \
           -configuration Release \
           -destination 'generic/platform=iOS' \
           -archivePath ./build/YourApp.xcarchive \
           clean archive | tee xcodebuild.log | xcpretty --color --report html

This may expose hidden build errors or code signing issues.

---

2. Check for Signing & Provisioning Issues

The log shows this line:

Automatically signing iOS for device deployment using specified development team in Xcode project

It suggests automatic signing is in use — but if your provisioning profile is mismatched, expired, or not available in the build environment, the archive will silently fail.

Try:

• Verifying that the provisioning profile and certificate are valid and installed in the CI runner/macOS environment.
• Confirming that the correct exportOptions.plist is being used (especially the method, teamID, and provisioningProfiles keys).

---

3. Run xcodebuild Locally with the Same Archive Command

Replicate the exact CI build command locally to see if you can reproduce the issue outside the CI environment. This often reveals environment-specific issues.

---

4. Check for Missing Build Artifacts

Sometimes a flutter build ipa or xcodebuild archive will return status 1 if:

• A script phase fails (e.g. Run Script in Xcode)
• A linked framework or plugin is missing
• Flutter doesn’t correctly generate iOS native code

To check:

flutter clean
flutter pub get
cd ios
pod install

Then try running the archive again.

---

5. Inspect Build Logs Directly

If possible, attach the raw xcodebuild.log or enable --verbose-system-logs with Flutter:

flutter build ipa --verbose --export-options-plist=...

This might reveal hidden warnings/errors before the exit code is returned.

---

Let me know if you'd like help reviewing any raw logs or if you're using third-party plugins — some may not be compatible with the latest Xcode or iOS SDK.

Hope this helps!

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬