Provisioning problem

Was struggling for hours before discovering this thread. The issue for me was for literally any app i tried to upload, not just one specific app. I did discover a workaround.

WORKAROUND:

1. Go to Certificates, Identifiers & Profiles
2. Create a profile that specifically targets your app bundle identifier
3. create the profile, download it
4. disable automatic profile management in xcode under Signing & Capabilities
5. Import newly downloaded profile

worked for me :)

the same issue!! run on device how long time need to fix ? @DTS Engineer

I'm guessing this has something to do with the new versions of Xcode and iOS that were in the middle of... Just got pushed an update.

same issue on mac mini building for ipad or iphone macOS Version 15.6 (Build 24G84) Xcode 16.0 (23051) (Build 16A242d) same result, and the provisioned profile used for the same app day before is gone from VPN and devices... there is no profile to trust it has gone. signed in out tried to reissue cert as per older forums guidance. that however resulted in different certificates for the same name in keychain now. however automatically manage signing picks the cert most recently issued which it deems valid and is aware of both valid certificates. however still says This provisioning profile does not have a valid signature (or it has a valid, but untrusted signature).)

I encountered the same issue but was able to resolve it. Please follow these steps:

1. Open Keychain Access on your Mac.
2. Locate your certificate and double-click it.
3. Navigate to the Trust section and set it to Always Trust.
4. Open Xcode and go to Signing & Certificates.
5. Click Try Again for the provisioning profile.
6. Run the app on your physical device.

Following these steps should resolve the issue.

3- Navigate to the Trust section and set it to Always Trust.

I’m not sure why that helped in your case but this is not a good idea. Modifying certificate trust settings is a common cause of errSecInternalComponent errors.

I’m back in the office and I’m gonna take another look at this again once I have a few minutes to spare.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

this worked for me from this stackoverflow post

1. Quit Xcode.
2. Go to ~/Library/Developer/Xcode/UserData/Provisioning Profiles and delete all your profiles. (my provisioning profiles directory is different, this is just copied from the stack post)
3. Relaunch Xcode.
4. Try again.

OK, a quick update…

IMPORTANT Please don’t post replies that just say ‘me too’. There’s a Boost button at the top of the thread that you can click in that case. OTOH, if you have new info to share, please post a reply, not a comment. It’s hard for me to keep track of comments.

My understanding of this issue is that:

• It was a problem with the way that the Developer website issued provisioning profiles.
• It had been resolved at the time I posted that response, about 4:00 Pacific time.

Hence my original advice on this thread to run a test with a new, unique bundle ID.

I just ran that test myself and I didn’t see a problem. Specifically:

1. Using Xcode 16.4 on macOS 15.6.1, I created a new project from the iOS > App template.
2. In Signing & Capabilities, I confirm that automatic code signing was enabled with my team selected.
3. I selected an iOS 18.6.2 device as the run destination and chose Product > Run.

The app ran just fine. However, this is using my extant wildcard provisioning profile, so it’s not a great test. I then extended the test:

1. In Signing & Capabilities, I added the Personal VPN capability. I don’t care about VPN here, but adding this capability forces Xcode to generate a new, non-wildcard profile for my app.
2. Once Xcode was done, I clicked the info button next to the Provisioning Profile field. It shows that the profile was created on 16 Sep 2025, confirming that Xcode has created a new profile for my app.
3. I chose Product > Run again. The app ran just fine.

This suggests that my understanding of this issue is correct, that is, it’s been resolved on the Developer website. However, there are lots of folks on this thread who are still having problems. I see two possibilities there:

• The problems are triggered by specific circumstances that I’m not testing. For example, I’m using Xcode 16 and other folks are using Xcode 26. I’m not set up to test with Xcode 26 right now, but I’ll try to do that ASAP. However, if this issue is what I think it is, Xcode 26 won’t change things.
• Their development environment is caching stuff and they need to find a way to clear the cache.

If you’re having problems, I recommend that you try to tease these possibilities apart by running the test I’ve described above. And, specifically, run the second test even if the first test fails. Please reply here to let me know what you discover.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

I started having this issue about 10 hours ago FWIW, on a provisional and on a paid developer account. I am unable to build for physical devices.

In reply to @DTS Engineer:

I am able to build my app with a new bundle ID, but not the already existing bundle ID. I am unable to confirm if also adding a capability fixed anything as I did this at the same time as changing the bundle ID unfortunately. However, I still have issues that I want to build my app with the current bundle ID.

The answer from Muslim Ismailov in Stack Overflow worked for me https://stackoverflow.com/a/79765898/14386923

The problems are triggered by specific circumstances that I’m not testing. For example, I’m using Xcode 16 and other folks are using Xcode 26. I’m not set up to test with Xcode 26 right now, but I’ll try to do that ASAP. However, if this issue is what I think it is, Xcode 26 won’t change things.

I believe that's the case. In Xcode 26 Automatic signing of all my apps for Ad Hoc distribution appears to be broken. The app archives and exports without errors, but all my devices refuse to install the app, complaining that "This provisioning profile does not have a valid signature (or it has a valid, but untrusted signature".

I manually created my own provisioning profiles for all the targets, switched from automatic to manual signing and everything works. It's like we're back in 2014 but at least I cut my teeth on all this stuff back in the day so I still remember all the steps required.

I have had the exact same problem with all projects for the last 12 hours :-/

However I just deleted ALL files and folders from .../Library/Developer/Xcode - which seems to have fixed the problem for me.

I'm using MacOS 15.7, Xcode 16.4 and iOS 18.7 on the iPhone I test on.

Cheers Thomas

I’m not set up to test with Xcode 26 right now, but I’ll try to do that ASAP.

I repeated the test described above with Xcode 26 RC and iOS 26.0, and things continue to work. Here’s a summary of my results:

Xcode   | iOS        | Result
-----   | ---        | ------
16.4    | iOS 18.6.2 | OK
26.0 RC | iOS 18.6.2 | OK
26.0 RC | iOS 26.0   | OK

This is all running on macOS 15.6.1, using a unique bundle ID each time.

At this point I’m pretty much convinced that the root cause of this issue is resolved and that the remaining problems are caused by Xcode caching bad state.

Unfortunately it’s hard for me to test solutions to that because I’ve never managed to reproduce the problem.

The answer from Muslim Ismailov in Stack Overflow worked for me

Cool. That’s very like what I described earlier.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

It was working fine on Xcode 26 RC and with iOS 26 RC devices yesterday. Today I upgraded to Xcode 26 (17A324), then this problem occurred.

Deleting all files from ~/Library/Developer/Xcode/UserData/Provisioning Profiles helps.