Totally noob programmer here, forgive me if this is a basic user error. But there seems to be a mismatch between my apple id identifier and my team identifier. It has been automatically configured, and worked until today, but while trying to run a new app on my iphone i all of a sudden got "Failed to install embedded profile for com.kylland.formattingtest : 0xe800801a (This provisioning profile does not have a valid signature (or it has a valid, but untrusted signature).)".
Now it does not work on any apps. Went through what chatgpt had to give me, trying to log in and out, made sure automatic signing is enabled and tried to delete the key from keychain. Still comes up with two different keys.
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:
- Using Xcode 16.4 on macOS 15.6.1, I created a new project from the iOS > App template.
- In Signing & Capabilities, I confirm that automatic code signing was enabled with my team selected.
- 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:
- 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.
- 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.
- 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"
