Xcode Build Failed, image_picker_ios is not found, signal sigabrt bug

[emir9922]

Steps to reproduce

Hi everyone,

I’m having a lot of trouble running my Flutter project on my physical iPhone. When I try to launch it using Xcode, I get several different errors — some disappear after a while, then come back again. I’ve tried many different solutions, but I’m still stuck.

Here are the details:

When I run the project from VSCode with my iPhone connected, the build succeeds, but the app crashes immediately with a Signal SIGABRT error. The app just shows a white screen on my phone and doesn’t open properly.

When I run the same project directly from Xcode, the build fails and I get an “image_picker_ios not found” error.

I tried the following commands to fix it:
rm -rf Pods Podfile.lock
pod cache clean --all
pod install

But the error persists.

I heard that the image_picker_ios package name has changed, but I checked every related file and everything already uses the correct image_picker_ios name — no old names remain.
Despite that, the issue continues.

Other errors I get when building with Xcode include:

Pods_Runner not found

Linker command failed

So basically:

VSCode → build succeeds, but app crashes (white screen, SIGABRT)

Xcode → build fails (image_picker_ios not found, linker command failed)

I think these issues may have started after some recent iOS updates — every update seems to cause new build issues 😅

If anyone has any idea how to fix these, I’d really appreciate your help.
Thank you in advance! 🙏

Expected results

The project should build successfully both in Xcode and VSCode, and the app should open normally on my iPhone without any errors (no Signal SIGABRT, no missing packages, no white screen).

Actual results

When I run the project from VSCode, the build succeeds but the app crashes with a Signal SIGABRT error and stays on a white screen.
When I run it from Xcode, the build fails with “image_picker_ios not found,” “Pods_Runner not found,” and “linker command failed” errors.

Code sample

Code sample

[Paste your code here]

Screenshots or Video

Screenshots / Video demonstration

[Upload media here]

Logs

Logs

[Paste your logs here]

Flutter Doctor output

Doctor output

[Paste your output here]

[emir9922]

this is my flutter doctor results
flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.32.5, on macOS 26.0.1 25A362 darwin-arm64, locale
tr-TR)
[✓] Android toolchain - develop for Android devices (Android SDK version 35.0.1)
[✓] Xcode - develop for iOS and macOS (Xcode 26.0.1)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2024.3)
[✓] VS Code (version 1.105.1)
[✓] Connected device (3 available)
[✓] Network resources

• No issues found!

this is my pod install results
pod install
Analyzing dependencies
Downloading dependencies
Generating Pods project
Integrating client project
Pod installation complete! There are 2 dependencies from the Podfile and 2 total pods installed.

[!] CocoaPods did not set the base configuration of your project because your project already has a custom config set. In order for CocoaPods integration to work at all, please either set the base configurations of the target Runner to Target Support Files/Pods-Runner/Pods-Runner.profile.xcconfig or include the Target Support Files/Pods-Runner/Pods-Runner.profile.xcconfig in your build configuration (Flutter/Release.xcconfig).

[darshankawar]

@emir9922 Can you try by creating a Flutter project, add image_picker to it and then try to run via Xcode and see if you still get same reported error or not ?

[emir9922]

I fixed the problem
I did these things:

flutter clean
rm -rf ios/Pods
rm ios/Podfile.lock
flutter pub get
cd ios
pod install --repo-update
cd ..

I ran these commands in Vscode terminal and then did to Xcode → Product → Clean Build Folder.

After doing this, the "Build Failed" error was resolved.

To fix the signal SIGABRT error, I updated Flutter, and all errors disappeared.

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.