dotnet / maui

.NET MAUI is the .NET Multi-platform App UI, a framework for building native device applications spanning mobile, tablet, and desktop.
https://dot.net/maui
MIT License
22.12k stars 1.73k forks source link

Codesign fails with replacing existing signature and errSecInternalComponent #25432

Open tpitman opened 2 hours ago

tpitman commented 2 hours ago

Description

I was using MAUI SDK 401. Everything was working fine. I got tired of dealing with VSCode issue and decided to switch to using VS 2022 on Windows on ARM in Parallels. I am on a Mac.

I had everything installed, but saw there was an update to 17.11.5. I installed the update and it seems that it installed an update to 8.0.403.

When I tried to debug with that it said I needed XCode 16. I had been holding off, but decided to go ahead and see if I could get this all working on the latest.

Long story short I am able to build and debug to an iOS physical device, but when I try to do a release build for distribution to the app store I get an error.

It happens during the codesign step.

I get 2 and they are happening on one of the framework files included in my app as far as I can tell. Here are the 2 lines for the errors:

Image

If I use the publish feature in VS 2022 for Windows it does build an archive, but when I try to upload it I get an error trying to upload it.

The command I use to do the build is:

dotnet publish -f net8.0-ios -c Release

That is the command I have been using ever since I had to stop using VS For Mac and it has worked fine until 8.0.403.

Now I am stuck and can't release the app update that I really need to update.

Please help. I am in a bad way right now.

Steps to Reproduce

  1. Build on command line for release.
  2. Get codesign error

Link to public reproduction project repository

No response

Version with bug

8.0.82 SR8.2

Is this a regression from previous behavior?

Yes, this used to work in .NET MAUI

Last version that worked well

8.0.70 SR7

Affected platforms

iOS

Affected platform versions

iOS 15

Did you find any workaround?

No

Relevant log output

No response

similar-issues-ai[bot] commented 2 hours ago

We've found some similar issues:

If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue.

Note: You can give me feedback by 👍 or 👎 this comment.