iOS Code Signing Error 0xe8008015 after adding Maps/Location capabilities on physical device

Targets iOS
1

Hi everyone,

I am running into a persistent code-signing blocking issue when trying to install my app on a physical iOS test device after adding new capabilities. My app previously built and deployed fine, but the installation now fails after enabling Maps, Location, Photos, and File Sharing.

My Environment:

  • Xojo Version: 2026r1

  • macOS Version: 26.5.1

  • Xcode Version: 26.6 (Build 17F113)

  • Account: Paid Apple Developer Account (up to date)

The Workflow & Error:
My standard workflow is hitting Build in Xojo (Build For is set to Development), then opening Xcode’s Devices and Simulators window and clicking the + icon under Installed Apps to push the compiled .app bundle.

When I do this, the install fails immediately with the following log error:
CoreDeviceError(errorCode: 3002) ... Code=13 "Failed to verify code signature ... 0xe8008015 (A valid provisioning profile for this executable was not found.)"

What I’ve Found:
If I manually drop my downloaded App Store/Development profile renamed as embedded.mobileprovision next to my Xojo project file, Xojo still doesn’t seem to bundle it or the entitlements natively.

The only way I can get the app onto my phone right now is to run a manual script via the Mac Terminal that forces an entitlement extraction from the profile, manually copies embedded.mobileprovision inside the compiled .app bundle, and runs a deep codesign command pointing to an extracted entitlements.plist.

When I run that manual Terminal override, the Xcode + button installs the app flawlessly and all the capabilities work. However, the next time I click Build in Xojo, the bundle is wiped clean and the signature breaks again.

My Info.plist properties (like UIFileSharingEnabled) are already set up inside Xojo’s Property List editor.

My Questions:

  1. Does Xojo not automatically package advanced hardware entitlements like com.apple.developer.maps into the binary signature layer when building for iOS?

  2. How do I format and link a custom entitlements.plist file within Xojo’s Build Settings so that Xojo natively includes these permissions during compilation without wiping them out?

Any guidance on how to make Xojo handle this natively so I can return to a smooth one-click build workflow would be greatly appreciated!

Thanks,
Sharon

2

I ran into a similar issue some time ago but never checked if it was fixed.

If you select build for App Store instead of Development, are you able to install the app on your test device?

What I found in the past is that doing a debug run on a physical device will not work when certain capabilities are added to the app. My understanding is that debug runs and Development builds use the same kind of code signing.