Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Flutter and app store releases

flutter run says: Could not run Runner.app, try Xcode Product > Run

ErrorCould not run build/ios/iphoneos/Runner.app on <device id>.

Short answer

Flutter prints this when installing or launching the built app on the iPhone fails, and it hides the real reason. Open ios/Runner.xcworkspace and press Product > Run in Xcode to see the actual error. The usual causes are Developer Mode off, a phone that does not trust the Mac, missing signing, or an untrusted certificate.

  • Applies to Flutter 3.x, Xcode 26, iOS 17+
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    Do what the message says. Open the workspace in Xcode, pick your iPhone and press Product > Run. Xcode shows the real error, which tells you which cause applies.

    open ios/Runner.xcworkspace
  2. 2Match what you see, then jump to its fix

    1. 1The Developer Mode switch is off, or the entry is missing in Settings > Privacy & SecurityDeveloper Mode is off on the iPhoneFix
    2. 2The Trust this computer prompt on the phone was never answeredThe phone has not trusted this MacFix
    3. 3Xcode shows a signing error when you press Product > RunThe app is not signed with a development certificateFix
    4. 4The certificate is not yet enabled under VPN & Device Management on the phoneThe developer certificate is not trusted on the phoneFix

What does the error look like?

  • Could not run build/ios/iphoneos/Runner.app on <device id>.
  • Try launching Xcode and selecting "Product > Run" to fix the problem:
  • open ios/Runner.xcworkspace

Cause 1 of 4

Developer Mode is off on the iPhone

1Check

On the phone, open Settings > Privacy & Security and look for Developer Mode. If the entry is not there, connect the phone, unlock it and trust the computer first.

flutter devices

2Fix

Turn Developer Mode on, restart the phone, then confirm Turn On when it asks. If the option is hidden, run flutter run or open Xcode once so it prepares the device.

flutter run -d <device_id>

3Verify

The phone appears in the device list and the app launches.

flutter devices

Confirmed by docs.flutter.dev

Did this fix it?

Cause 2 of 4

The phone has not trusted this Mac

1Check

On first connection the phone shows Trust this computer. Unlock the phone and look for the prompt.

flutter devices

2Fix

Unplug, unlock the phone, reconnect and tap Trust.

flutter doctor -v

3Verify

flutter devices lists the iPhone as a connected device.

flutter devices

Confirmed by docs.flutter.dev

Did this fix it?

Cause 3 of 4

The app is not signed with a development certificate

1Check

Flutter's setup guide says a signed developer certificate is needed even for testing. A free personal Apple developer account is enough for that.

open ios/Runner.xcworkspace

2Fix

Sign in with your Apple ID in Xcode and set up signing for the Runner target as the iOS setup guide describes, then run again.

flutter run -d <device_id>

3Verify

The build installs on the phone.

flutter run -d <device_id>

Confirmed by docs.flutter.dev

Did this fix it?

Cause 4 of 4

The developer certificate is not trusted on the phone

1Check

Open Settings > VPN & Device Management on the phone and look under Developer App.

# on the iPhone: Settings > VPN & Device Management

2Fix

Tap your certificate there, then tap Trust and confirm. If the menu is missing, run the app on the device once and look again.

flutter run -d <device_id>

3Verify

The app opens on the phone.

flutter run -d <device_id>

Confirmed by docs.flutter.dev

Did this fix it?

How do I stop it coming back?

  • Keep the Mac and phone connected and unlocked for the first run after an iOS update.
  • On a new device, connect it, unlock it and trust the Mac, then run once from Xcode or flutter run so the device is prepared.
  • Read Xcode's error, not Flutter's summary line, when an install fails.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.

Which stack is behind this page?

Projects of mine built on the same technologies:

Related fixes

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.