5,381 questions
Error: Failed to codesign 'bin/iPhone/Release/[APPNAME].app//Frameworks/protobuf.framework/protobuf': Warning: unable to build chain to self-signed root for signer "Apple Development:
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(48, 88%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EU%3C/text%3E%3C/svg%3E)
Uttam
6
Reputation points
I am getting this error while build app on VS2019 Community for Mac, Xamarin. I have the latest updates for VS & Xamarin.
I also applied the cert mentioned here. https://developer.apple.com/support/expiration
The build goes well when I am in Release mode, but when I change it to Release|iPhone and connect my iPhone I get the following error.
/Library/Frameworks/Mono.framework/External/xbuild/Xamarin/iOS/Xamarin.Shared.targets(3,3): Error: Failed to codesign 'bin/iPhone/Release/[APPNAME].app//Frameworks/protobuf.framework/protobuf': Warning: unable to build chain to self-signed root for signer "Apple Development: Mike Popplewell (82WT7P52FZ)"
I checked the Project->Options->iOS Bundle Signing ->Signing Identity: Developer. Everything looks good here.
Any help is much appreciated.
Developer technologies | .NET | Xamarin
{count} vote
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(281.6, 23%, 37%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKW%3C/text%3E%3C/svg%3E)
Kyle Wang 5,531 Reputation points Microsoft External Staff2021-07-15T03:03:20.483+00:00 @Uttam Try to open the KeyChain Access and right click Apple Worldwide Developer Relations Certificate Authority. Then select "Get Info", change the selection in "Trust->When using this certificate" to "Use System Default". Then try to clean the solution and re-download the Profiles. Here found a similar thread maybe you can refer to.
-
Uttam 6 Reputation points
2021-07-15T17:09:25.507+00:00 @Kyle Wang its still not working. Is there anyway I can contact you?
-
Kyle Wang 5,531 Reputation points Microsoft External Staff
2021-07-16T09:41:44.047+00:00 @Uttam Since this issue can't be reproduced, try to report a problem on Developer Community or submit an issue on Github.
Sign in to comment
Sign in to answer