Bug 59092 - Double slash in OutputPath property crashes iOS app build on Mac with error ArgumentException: Second path fragment must not be a drive or UNC name.
Summary: Double slash in OutputPath property crashes iOS app build on Mac with error A...
Status: CONFIRMED
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: General ()
Version: 4.6.0 (15.3)
Hardware: PC Windows
: --- major
Target Milestone: 15.6
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2017-08-29 14:13 UTC by patrickhofman
Modified: 2017-08-30 18:03 UTC (History)
4 users (show)

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


Attachments
Test case (302.09 KB, application/x-zip-compressed)
2017-08-30 05:32 UTC, Prashant [MSFT]
Details


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 for Bug 59092 on Developer Community if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: Developer Community HTML
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.
Related Links:
Status:
CONFIRMED

Description patrickhofman 2017-08-29 14:13:08 UTC
# Steps to reproduce
1. Create a new Xamarin iOS Single View app in Visual Studio 2017 Update 3;
2. Using Notepad, change the OutputPath property to <OutputPath>$(SolutionDir)\bin\</OutputPath> ;
3. Compile the project with a Mac;
4. Error (see below).

# Expected behavior
Changing the OutputPath to <OutputPath>$(SolutionDir)bin\</OutputPath> makes it compile again. So expect resiliency against this user bug.

# Actual behavior
Building fails.

# Supplemental info (logs, images, videos)
2>...\Xamarin.iOS.Common.targets(1665,3): warning : An error occured on the receiver while executing a post for topic xvs/Build/4.6.0.299/execute-task/My.iOS.TestApp/962da94%2FCodesignNativeLibraries and client build1176Patri
2>...\Xamarin.iOS.Common.targets(1665,3): warning : An error occured on client Build460299 while executing a reply for topic xvs/Build/4.6.0.299/execute-task/My.iOS.TestApp/962da94%2FCodesignNativeLibraries
2>...\Xamarin.iOS.Common.targets(1665,3): warning :    at Xamarin.Messaging.Client.MessagingClient.<PostAsync>d__23`2.MoveNext() in C:\d\lanes\4985\b63523e2\source\xamarinvs\src\Messaging\Xamarin.Messaging.Client\MessagingClient.cs:line 179
2>...\Xamarin.iOS.Common.targets(1665,3): error : MessagingRemoteException: An error occured on client Build460299 while executing a reply for topic xvs/Build/4.6.0.299/execute-task/My.iOS.TestApp/962da94%2FCodesignNativeLibraries
2>...\Xamarin.iOS.Common.targets(1665,3): error : ArgumentException: Second path fragment must not be a drive or UNC name.
2>...\Xamarin.iOS.Common.targets(1665,3): error : Parameter name: path2

# Test environment (full version information)

Microsoft Visual Studio Professional 2017 
Version 15.3.2
VisualStudio.15.Release/15.3.2+26730.10
Microsoft .NET Framework
Version 4.7.02046

Installed Version: Professional

Xamarin   4.6.0.299 (b63523e27)
Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android.

Xamarin.Android SDK   7.4.0.21 (2851083)
Xamarin.Android Reference Assemblies and MSBuild support.

Xamarin.iOS and Xamarin.Mac SDK   10.12.0.20 (80b8487)
Xamarin.iOS and Xamarin.Mac Reference Assemblies and MSBuild support.

Mac OS Sierra 10.12.6, Mac mini (Late 2014)
XCode 8.3.3
Comment 1 Prashant [MSFT] 2017-08-30 05:32:24 UTC
Created attachment 24468 [details]
Test case

Thanks so much for taking the time to submit this report! I can confirm using the latest Visual Studio 2017 stable version 15.3.2 

I am able to reproduce this issue. Marking this report as CONFIRMED. 

Attached the Test case

# Version Information

Microsoft Visual Studio Enterprise 2017 
Version 15.3.2
VisualStudio.15.Release/15.3.2+26730.10
Microsoft .NET Framework
Version 4.7.02046

Installed Version: Enterprise

Xamarin   4.6.0.299 (b63523e27)
Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android.

Xamarin Sample Importer   1.0
Open Xamarin mobile samples directly on Visual Studio

Xamarin.Android SDK   7.4.0.21 (2851083)
Xamarin.Android Reference Assemblies and MSBuild support.

Xamarin.iOS and Xamarin.Mac SDK   10.12.0.20 (80b8487)
Xamarin.iOS and Xamarin.Mac Reference Assemblies and MSBuild support.