Bug 59801 - Say Goodbyte Target still failig when building an iOS project
Summary: Say Goodbyte Target still failig when building an iOS project
Status: RESOLVED NORESPONSE
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: iOS ()
Version: 4.7.0 (15.4)
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2017-09-27 20:26 UTC by David
Modified: 2017-10-13 03:15 UTC (History)
5 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED NORESPONSE

Description David 2017-09-27 20:26:15 UTC
Bug 54654 is marked as resolved. it is NOT resolved, so opening new bug.

VS2017  v 15.3.5
Xamarin 4.7.9.45
Xamarin.ios version 11.0.0.0
running on Mac under Parallels

VSfM 7.1.5 build 2
Xamrin.iOS 11.0.0.0

Output (identifiable names reaplced with x's):

5>xxxx.xxxx.Common.iOS -> C:\Work\Dev\xx\xx\src\xxxx.xxxx.Common.iOS\bin\Debug\xamarin.ios1.0\xxxx.xxxx.Common.iOS.dll
5>C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\Xamarin\iOS\Xamarin.iOS.Windows.After.targets(90,5): warning : An error occurred getting directory checksum for App {0}
5>C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\Xamarin\iOS\Xamarin.iOS.Windows.After.targets(90,5): warning : Value cannot be null.
5>C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\Xamarin\iOS\Xamarin.iOS.Windows.After.targets(90,5): warning : Parameter name: path3
5>C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\Xamarin\iOS\Xamarin.iOS.Windows.After.targets(90,5): warning :    at System.IO.Path.Combine(String path1, String path2, String path3, String path4)
5>C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\Xamarin\iOS\Xamarin.iOS.Windows.After.targets(90,5): warning :    at Xamarin.Messaging.PlatformPath.GetServerBuildPath(String home, String appName, String sessionId, String path) in C:\d\lanes\5126\bd7e3753\source\xamarinvs\src\Messaging\Xamarin.Messaging.Common\PlatformPath.cs:line 51
5>C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\Xamarin\iOS\Xamarin.iOS.Windows.After.targets(90,5): warning :    at Xamarin.Messaging.Ssh.SshService.<GetDirectoryChecksumAsync>d__15.MoveNext() in C:\d\lanes\5126\bd7e3753\source\xamarinvs\src\Messaging\Xamarin.Messaging.Ssh\SshService.cs:line 74
5>C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\Xamarin\iOS\Xamarin.iOS.Windows.After.targets(90,5): error : One or more errors occurred.
5>Done building project "xxxx.xxxx.Common.iOS.csproj" -- FAILED.



Come on guys, fix the bug. You've had a long time to get to the bottom of this and fix it. A work around is NOT a solution.
Comment 1 David 2017-09-27 20:33:43 UTC
Quiting VS2017 and restating sometimes resolves he issue, but it seems random whether this works or not.
Comment 2 Jimmy [MSFT] 2017-09-28 22:16:44 UTC
How often are you seeing this error? If you are able to build successfully at times, can you gather the verbose build output from the successful build as well as the output from a failed build? If the workaround from bug 54654 does help then the question is why that parameter results in being empty and comparing the two outputs may give us an answer.

Follow these steps to enable the verbose build output: https://developer.xamarin.com/guides/cross-platform/troubleshooting/questions/version-logs/#verbose-build-output-logs

And please also include the Xamarin logs by going to Help > Xamarin > Zip logs (last 7 days) inside Visual Studio. You can attach the items to this report or feel free to send them via my email address listed on here instead. Thanks!
Comment 3 Pierce Boggan [MSFT] 2017-10-13 03:15:33 UTC
Thanks for taking the time to file this issue! :)

Because we have not received a response for over 14 days, we are marking this issue as RESOLVED->NOREPONSE. If you hit this issue again, please don't hestitate to reopen this ticket with the information requested above. 

Thanks again, 
The Xamarin Team