Introduction

When Xcode says "Could not launch" and the only clue is "Security", the problem is usually not your app logic. It is typically a signing, provisioning, entitlement, or device-trust issue that prevents iOS from accepting the app for installation or debugging.

What "Security" Usually Points To

The launch path from Xcode to a physical device involves several security checks:

• the app must be signed with a valid development identity
• the provisioning profile must match the bundle identifier and target device
• the device must allow development builds
• the app's entitlements must be compatible with the profile

If any of those pieces are wrong, Xcode may fail with a very vague "Security" message.

On current Apple platforms, Developer Mode is also part of the story for running and debugging apps on devices during development. Apple documents that Developer Mode is required on supported device versions for installing, running, and debugging development builds.

Start with Signing and Provisioning

The first thing to verify is that the app is signed for development, not App Store distribution. Apple notes in its code-signing troubleshooting material that builds signed with an App Store profile do not run on devices through Xcode.

In Xcode, check:

• the selected team
• the bundle identifier
• whether automatic signing is enabled
• the profile and certificate used for the active build configuration

If you use manual signing, make sure the provisioning profile actually contains the connected device and matches the app ID. If the device was disabled or added after the profile was generated, the profile may be stale.

Useful command-line checks:

security find-identity -v -p codesigning

That lists code-signing identities installed on the Mac.

To inspect the signed app's entitlements:

codesign -d --entitlements :- /path/to/MyApp.app

If the signed entitlements do not match what the profile allows, launch can fail before your app ever runs.

Check the Device Side

If you are deploying to a real iPhone or iPad, verify that the device is trusted by the Mac and available for development. On newer platform versions, also confirm Developer Mode is enabled on the device.

This matters because Xcode can build successfully and still fail at install or launch time if the device is not prepared for development. That kind of failure often looks unrelated to your code because it happens before the app process starts.

If the device was recently updated, reconnect it, unlock it, and confirm any trust prompts again. Then retry from Xcode after the device has finished indexing and setup tasks.

Entitlements and Capability Mismatches

Another common source of "Security" launch failures is an entitlement mismatch. For example, enabling a capability in the target can cause Xcode to sign the app with entitlements that the provisioning profile does not support.

A simplified entitlement snippet might look like this:

1<?xml version="1.0" encoding="UTF-8"?>
2<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
3<plist version="1.0">
4<dict>
5    <key>aps-environment</key>
6    <string>development</string>
7</dict>
8</plist>

If push notifications are enabled in the app but not configured for the App ID and profile, signing can succeed imperfectly while launch still fails on device.

The same idea applies to associated domains, iCloud, app groups, and other protected capabilities. If you changed capabilities recently, regenerate the profile or let Xcode refresh signing automatically.

Where to Get Better Diagnostics

The Xcode popup is often too vague to be useful. Better diagnostics usually come from:

• the device logs in Xcode's Devices window
• the build log details for signing and validation
• the macOS Console app while attempting the launch

Those logs may reveal the real root cause, such as:

• invalid code signature
• missing entitlement
• profile mismatch
• device not provisioned for development

If the app installs on the simulator but not on a physical device, that is a strong signal that signing or device configuration is involved. Simulator builds are not signed in the same way as device builds.

A Practical Recovery Checklist

When the error is vague, a short recovery loop is often faster than guessing:

1. confirm the selected run destination is the intended physical device
2. enable automatic signing temporarily if possible
3. reconnect and unlock the device
4. verify Developer Mode on supported device versions
5. clean the build folder and rebuild
6. refresh profiles or re-download signing assets

If that still fails, compare the app's entitlements and profile more closely using the command-line tools above.

Common Pitfalls

The first mistake is debugging application code before confirming the app actually launched. A "Security" error usually means the app never got that far.

Another common issue is signing with the wrong profile type. Development builds for device testing need a development-capable setup, not an App Store distribution profile.

Developers also overlook Developer Mode and device trust on modern iOS versions, especially after upgrading the device or switching Macs.

Finally, capability changes are easy to forget. Turning on push notifications, iCloud, or app groups can invalidate an otherwise working signing configuration.

Summary

• Xcode "Could not launch" with "Security" usually means signing or device-trust problems, not app-code bugs.
• Check development signing, provisioning profile validity, device registration, and entitlements first.
• On modern iOS devices, Developer Mode must be enabled for development installs and debugging.
• Use security and codesign command-line tools plus device logs to get the real cause.
• Simulator success does not rule out device-signing failures.