Debug Profile Suddenly not working

[tpitman]

Apple platform

iOS

Framework version

net9.0-*

Affected platform version

VS 2022 17.14.13, VSCode with latest Extensions.

Description

This morning I was debugging using VS 2022 in Parallels on my mac to an iPhone.

This afternoon I am suddenly getting and error that the exact same provisioning profile isn't valid.

Nothing has changed. I just hit debug in VS 2022 or in VSCode and get this error:

Failed to install embedded profile for com.blah : 0xe800801a (This provisioning profile does not have a valid signature (or it has a valid, but untrusted signature).) (MIInstallerErrorDomain error 13 (0x0D))

I tried creating a new profile and get the same error.

The only thing I did between this morning and this afternoon as updated my MacOS to 15.7.

Can this have something to do with Apple releasing Xcode 26 and new versions of all the OS's today?

I do NOT automatically update my Xcode. I am still using Xcode 16.4 that I was using this morning that was working.

As I said the only thing I did was update the OS to 15.7. I am not planning on upgrading to the new MacOS 26 until I have to.

Steps to Reproduce

n/a

Did you find any workaround?

no

Relevant logs

No response

[rolfbjarne]

Most likely the provisioning profile you were using expired, and then the build picked up another one, which didn't work (doesn't have the necessary entitlements). My guess is that the new provisioning profile you created doesn't have the right entitlements either.

The easiest way to fix this is probably to look at all your provisioning profiles on Apple's website, find the one(s) that expired today, and then renew and download that one.

Can you try that? If it doesn't work, please provide an MSBuild binlog.

[tpitman]

I might not have been clear, this is the automatic provisioning profile that gets created as needed by Visual Studio 2022 for Windows (in Parallels) when I hit Debug to my iOS device.

As far as I can tell it gets automatically updated each time I debug.

I tried another app that I can debug fine and the date created on the provisioning profile was updated to today's date even though it was already valid.

Not sure about how all that works. I have these apps set to automatic provisioning.

I don't know where I would control the entitlements requested in this case. None of that has changed in any of the files that I know of.

As I said in the original post, I was hitting debug in the morning and it was working fine, then in the afternoon it just stopped working.

Is it safe to upload a binlog to a public issue here on github? I don't want any information to leak that might be contained in it....

[tpitman]

New information. It suddenly started working.

I tried it as part of building and getting the binlogs. I installed that binlog extension to VS2022. I turned on the Diagnostic settings for building.

I then built again and it installed and debugged just fine.

I also see that a new provisioning profile was automatically created in my developer account. I had not deleted or editing that at all.

VS 2022 automatically did this.

I can't help but wonder if Apple had something going on with all the released where it created a bad profile for me yesterday and somehow a few minutes ago VS detected something or did something to generate a new one and whatever was wrong yesterday was fixed by Apple.

I guess we will keep an eye on it...

[rolfbjarne]

I can't help but wonder if Apple had something going on with all the released where it created a bad profile for me yesterday and somehow a few minutes ago VS detected something or did something to generate a new one and whatever was wrong yesterday was fixed by Apple.

It wouldn't be the first time something like this happened...

I guess we will keep an eye on it...

I'll close it for now, but if you run into this again let us know and we can reopen.