iOS-deploy fails after macOS upgrade: “A valid provisioning profile for this executable was not found”

Solar2D iOS
#1

I can install a colleague’s .app bundle on my test iPhone with ios-deploy just fine, but my own build of the exact same project fails with:

Error 0xe8008015: A valid provisioning profile for this executable was not found.

This started right after I upgraded to Tahoe. I tried with both Xcode 16 and 26 and their corresponding Solar2D versions.

I build my app using the CLI and not in the Engine.

What I’ve Checked

  • Compared my .app bundle with my colleague’s:
    • All entitlements, embedded.mobileprovision contents, signing certificates and nested code objects are identical (only the CFBundleVersion differs).
  • Verified the provisioning profile:
    • Device UDID is present
    • Profile is a valid Development profile and not expired
    • Developer certificate fingerprint matches the one that signed the app
  • codesign --verify --deep --strict passes for all nested frameworks/extensions.

Symptom

  • My colleague’s build installs and runs fine on the same device with the same provisioning profile.
  • My build fails on 50% install with 0xe8008015.

Question

Has anyone seen 0xe8008015 after upgrading to Tahoe?

Could this be a new Xcode/Tahoe signing quirk or cache issue (e.g. derived data, stale developer certificates), or is there some new requirement I might be missing?

Any insights or troubleshooting steps beyond the standard codesign/profile checks would be greatly appreciated.

Solar2D 2025.3725 has been released
#2

Is the iOS simulator downloaded? Why that should be necessary I have no idea, but it seems you have to download the latest simulator every time you update XCode or you’ll run into weird build issues. I’ve also had problems with the command line tools not being installed or updated correctly, so it’s worth checking that too.

#3

Thanks @pokease, I just made sure both the simulator and CLI are both over 26.0 and yeah they are, but the error persists. :confused:

I also tried with the new Solar 3724 build, it’s the same.

Also mono sounds are not working neither. which makes things even more strange, I’m considering formatting my computer…

#4

I hate updating MacOS / Xcode for this reason, they constantly break things.

I’ve had exactly this problem before, and it was because either MacOS or Xcode changed the location that they look for the provisioning profiles.
In my case they used to be here:
/Users/alan/Library/MobileDevice/Provisioning Profiles/blah-blah-blah.mobileprovision

and then suddenly they needed to be here instead:
/Users/alan/Library/Developer/Xcode/UserData/Provisioning Profiles/blah-blah-blah.mobileprovision

Of course the update process didn’t perform any kind of auto-migration for those files, so the only way to find this out is to encounter the problem…

#5

I am having issues as well. Im on iOS 26 and MacOS Tahoe

I ran this command against my built .app file

codesign -d --entitlements :- ~/Desktop/game.app

And i notice this is in there. This value needs to be true to run in debug mode on a device. I am using a dev provisioning profile so im not sure why this is giving me issues.

get-task-allow

#6

I got around this by doing an ad hoc distribution certificate / profile instead of the dev one.

#7

Thanks @alanFlickGames and @tameem50 I tried your suggestions and invested way more time into understanding this that I would like to, but I finally came to the solution!

For some reason after the upgrade the plutil extract for the get-fast-allow didn’t work the same way for me and the app was getting signed with an incorrect value.

I PRed a fix here: Fix incorrect extraction of the get-task-allow flag from the provisioning profile by depilz · Pull Request #850 · coronalabs/corona · GitHub

I even formatted my Mac :laughing: but I’m glad it finally works again.