[Bug] "codesign" exited with code 1 iOS #6813
Comments
|
Thank you for your feedback! For us to investigate this further, could you please provide your full build logs and all your version information. To get full build logs just set the log verbosity to diagnostic at the following menu location: Tools > Options > Projects and Solutions > Build and Run You also want to add The easiest way to get exact version information: "Help menu", "About Microsoft Visual Studio" item. Then copy/paste the version information (you can use the "Copy Information" button). We look forward to hearing from you! |
rolfbjarne
added
bug
|
Hi thanks for the Help. Here are my logs and data. ########################################################################## Microsoft Visual Studio Enterprise 2019 (2) Installierte Version: Enterprise Architekturdiagramme und Analysetools 00433-90000-08078-AA000 Visual C++ 2019 00433-90000-08078-AA000 Allgemeine Azure-Tools 1.10 Application Insights-Tools für Visual Studio-Paket 9.1.00611.1 ASP.NET and Web Tools 2019 16.2.292.25104 ASP.NET Web Frameworks and Tools 2019 16.2.292.25104 Azure App Service-Tools v3.0.0 16.2.292.25104 Azure Functions and Web Jobs Tools 16.2.292.25104 C#-Tools 3.2.1-beta4-19408-03+2fc6a04980f800c59e8ede97e6ae294ff47d666e Erweiterung zum Debuggen von Momentaufnahmen 1.0 Extensibility Message Bus 1.2.0 (d16-2@8b56e20) GitHub.VisualStudio 2.9.1.7781 IntelliCode-Erweiterung 1.0 Microsoft Azure-Tools 2.9 Microsoft Continuous Delivery Tools für Visual Studio 0.4 Microsoft JVM Debugger 1.0 Microsoft MI-Based Debugger 1.0 Microsoft Visual C++-Assistenten 1.0 Microsoft Visual Studio-Tools für Container 1.1 Mono Debugging for Visual Studio 16.2.6 (4cfc7c3) NuGet-Paket-Manager 5.2.0 ProjectServicesPackage Extension 1.0 ResourcePackage-Erweiterung 1.0 ResourcePackage-Erweiterung 1.0 SQL Server Data Tools 16.0.61906.28070 Test Adapter for Boost.Test 1.0 Testadapter für Google Test 1.0 TypeScript-Tools 16.0.10627.2001 VC-Paket für Microsoft Visual Studio 1.0 Visual Basic-Tools 3.2.1-beta4-19408-03+2fc6a04980f800c59e8ede97e6ae294ff47d666e Visual F# Tools 10.4 für F# 4.6 16.2.0-beta.19321.1+a24d94ecf97d0d69d4fbe6b8b10cd1f97737fff4 Visual Studio-Tools für CMake 1.0 Visual Studio-Tools für CMake 1.0 Visual Studio-Tools für Container 1.0 Visual Studio Code-Debugadapter-Hostpaket 1.0 VisualStudio.Mac 1.0 Xamarin 16.2.0.95 (d16-2@37df81894) Xamarin Designer 16.2.0.375 (remotes/origin/d16-2@357d38ef4) Xamarin Templates 16.3.117 (59a59e8) Xamarin.Android SDK 9.4.1.1 (d16-2/cec9eb4) Xamarin.iOS and Xamarin.Mac SDK 12.14.0.114 (c669116) ########################################################################### Thank you Agredo |
|
Could you also attach the complete build log? It's not saved in the logs directory, you'll have to open the build log tab in the IDE and copy the text. |
|
Seeing this issue too. I can work round it with the following steps Get code1 error Seen this bug come and go in Visual Studio since the dark days of 2015 |
|
Same here, I typically get the codesign error after doing a full rebuild. It then goes away after switching from manual to automatic provisioning (or vice versa, depending on which was currently set). So it's not specific to one type of provisioning profile. It seems more related to the profile not being applied correctly during a rebuild, or being overwritten/lost during a later step, but then after changing the setting to trigger VS to re-apply the provisioning profile and doing a build, not rebuild, things then work because whatever was causing it to break during the rebuild step doesn't happen on a normal build. |
|
Getting this error and very annoying as the only way I can fix it is by doing a clean between every build. Any update on this? Doing a full build every time to test is no way to work. I've deleted the certs from keychain and re-added, full reboots etc. Nothing helps. Using the latest version of everything except windows which is Windows 7. Trying to deploy to a late 2018 iPad Pro Also for reference here is the output: |
|
For anybody who can reproduce this: please get a diagnostic build log from both a working and a failing build, and attach both build logs here. To get diagnostic build logs set the log verbosity to diagnostic at the following menu location: Tools > Options > Projects and Solutions > Build and Run You also want to add -v -v -v -v to the mtouch additional arguments by right-clicking the project in the solution explorer and selecting Properties. |
|
Here you go |
|
@VividDigital thank you for the build logs! A fix is in progress: #7332. |
|
Great. Thanks for the quick response. |
|
When can we expect the next update to be pushed out? This bug is really slowing down development |
|
Following up.... |
|
Also eagerly awaiting this to be fixed, as it's the biggest annoyance developing for iOS on Windows at the moment.. My build host is very slow, so whenever this happens I spend an hour trying to rebuild with different settings until it suddenly works again. |
|
visual studio 2019 Version: 16.3.9 |
|
VS 2019 16.3.10. The problem still persists |
|
This is supposed to be fixed in the new preview as seen here: https://developercommunity.visualstudio.com/content/problem/729766/codedesign-exited-with-code-1.html?childToView=842480#comment-842480 It is NOT fixed. How long is this going to take? This bug makes it pretty much impossible to work if your app is sizable at all. |
|
@VividDigital I'm sorry that you're still encountering this issue. There's a workaround in the forum post you linked: We’ve detected this issue is easily reproducible when using copy always for any file, so if any of your files has the Copy to Output Directory property set to Always we recommend you to change it to Copy if newer. This is a workaround but also a recommendation since using copy always might have a negative impact on the build performance. Please let us know if that works. |
|
@VividDigital - The best way to track the progress of the fix is by following the dev community thread: https://developercommunity.visualstudio.com/content/problem/729766/codedesign-exited-with-code-1.html?childToView=842480#comment-842480 Closing this GH issue as there is nothing actionable for the MaciOS team and it is tracked in DevOps. |
|
is there any solution for this problem |
|
@saidalsaidi There is a workaround posted in this comment: #6813 (comment) You can track progress on a fix here: https://developercommunity.visualstudio.com/content/problem/729766/codedesign-exited-with-code-1.html?childToView=842480#comment-842480 It looks like it has been fixed in Visual Studio 2019 version 16.5 Preview 1. Could you please try downloading Visual Studio 2019 version 16.5 Preview 1 and let us know whether the issue still occurs? |
|
i was having this issue, downloaded VS 2019 v16.5 Preview 1 and that fixed the problem |
|
I am on VS 16.5.2 and am seeing this issue now. |
|
downloaded the latest vs and still see this issue |
|
Also downloaded the RC 16.7 Preview 1.0, and it is itermittent - sometimes this error occurs, or not at all the first build / archive - but the constantly unable to build there afterwoulds, and looking for answers here again. Anyone have any stable luck ? I am building on a older mac mini, and was thinking if upgrading the device to a new 6 core i7 might help things - its painfully slow to build and then have to wait for this to never actually finish a complete build - where as 20 minutes ago on the previous build, it worked fine (still takes ages to compile though) |
|
Getting the same error for the 100th time, nothing I do will fix it. I hate the day I have to deal with Apple, unecessary and annoying as *****. |
|
Any progress on this? I can't bundle my app because i MUST clear the solution for every build process and looks like the bundling executes it twice (or at least executes twice the stuff that triggers this error). |
|
@pietrodicaprio you're probably running into a different underlying issue than the one originally reported here (because this one has been fixed), so please file a new issue, and please get a diagnostic build log from both a working and a failing build (as described here), and attach both build logs in the new issue. |
|
Just got this issue, running VS 16.11.4. Workaround to shift between automatic and manual provisioning seems to work, |
ghost
locked as resolved and limited conversation to collaborators
Sometimes during deploying, VS2019 stops with error: "codesign" exited with code 1
Steps to Reproduce
Basic Information
This Happens with the newest VS2019 and XF4.1 (Both not beta)
For more Information: https://stackoverflow.com/questions/48575062/xamarin-ios-error-msb6006-codesign-exited-with-code-1
The fix is very annoying:
Jul 3 at 20:32
Mephisztoe (Stackoverflow)
The text was updated successfully, but these errors were encountered: