Skip to content

Conversation

@tondat
Copy link
Contributor

@tondat tondat commented Jun 27, 2019

…if the AndroidSdk path is null

fixes bug 938504: AndroidSdk initialization fails with a System.ArgumentNullException when no AndroidSdk is detected on the user machine
https://devdiv.visualstudio.com/DevDiv/_workitems/edit/938504
@jonpryor
Copy link
Contributor

https://xamarinhq.slack.com/archives/C58CYJTMY/p1561656927244700

The ArgumentNullException is annoying, granted, but if we "fix" it we'll just emit an InvalidOperationException instead, from the AndroidSdkInfo constructor (as the Android SDK path will be null).

I thus don't see why we need this PR. It might be "nice to have" -- InvalidOperationException stating that the Android SDK couldn't be found instead of an ArgumentNullException from Path.Combine() -- but that's not necessary.

@joj
Copy link
Member

joj commented Jul 17, 2019

I think the more detailed error is useful. Agreed we don't need to rush it for 16.3, but I would like to see this in master and released whenever.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants