.NET Core on macOS High Sierra

[richlander]

We are currently testing .NET Core 1.x and 2.0 on High Sierra. Please post issues here.

See: dotnet/announcements#22

[jobrien721]

When using IdentityServer4 and developing in macOS High Sierra with .NetCore Version 2.0.0 preview 1, It just randomly Stops the "MVC" (Web Application with Membership and Authorization)project. However the Web API project works fine and has no problem. MVC is on port 5000 the API is on 49996 as some additional Information.Also when running the Identity Server Locally It will allow me to at least get to the Login Page but then this pops up after typing in credentials.

Before I updated to .NetCore 2.0 I was getting other errors which upgrading my .NetCore got rid of.

[bartonjs]

@jobrien721 Does it happen right away, or is it after the process has been running for several minutes?

[jobrien721]

@bartonjs it happens right away, and thank you for the response

[bartonjs]

@jobrien721 Hmm. Maybe they decreased the auto-lock timeout. I think this is fixed for preview2 by dotnet/corefx#20577. I think the links from https://github.com/dotnet/cli/blob/release/2.0.0/README.md will let you get a current/almost-preview2 build.

[jobrien721]

OK, thank you! I will check it out and let you know!

[jobrien721]

@bartonjs I just wanted to let you know, That updating to .NetCore 2.0.0-preview2 Did the fix for the Identity server and MVC issue! Im now facing another issue with the API, but with that said im gonna try to figure It out! If it becomes a huge problem I will post it here and if I solve it I will post it here if its not something small that I may have missed! Thank you again for your help!

[Petermarcu]

Going to close this issue because it looks like this one was resolved.

[jobrien721]

@Petermarcu Yes it is solved thank you but I believe I found another bug when running it locally it works perfectly fine(IdentityServer4,MVC, and API) however if I have the MVC or API try to hit the https Identity Server it Crashes and If I have the MVC try to point to the https API url it crashes as well. So my assumption at this point without further testing would be it may have something to do with the routing to a https. Im not sure if it is just https or http as well but I thought I would mention it.

Thank you in advance for your time!

[Petermarcu]

@jobrien721 , can you share a callstack of the crash?

[jobrien721]

@Petermarcu
First off the Image above is the box its in but this is whats inside..
Process: dotnet [2651]
Path: /usr/local/share/dotnet/dotnet
Identifier: dotnet
Version: 0
Code Type: X86-64 (Native)
Parent Process: dotnet [2645]
Responsible: dotnet [2651]

There is more info but some is private info about my Max and what not..Thats the gist of the top part tho then theres a full CallStack with .dylib info etc. . .

[Petermarcu]

The full callstack with Dylibs would be really helpful. Is there an easy way for you to sanitize it?

[jobrien721]

yes I will try to sanitize it and and get it to you this evening or tomorrow morning!

[Petermarcu]

Thanks! @wfurt and @bartonjs as FYI when to take a look when we you share more data.

[gu3st]

Hi:

Attached is a crash log that I'm seeing in High Sierra. It appears to occur when Crypto is attempted in High Sierra.

This is with dotnet core 1.1

dotnet_2017-06-19-182626_Gu3sts.crash.txt

[wfurt]

core 1.1. has known problem @gu3st . Can you reproduce it with 2.0 preview? @bartonjs submitted fix for 1.0 and 1.1 and it is in testing right now. There is no pre-built binary yet AFAIK.

[gu3st]

I tried with 2.0, but my project doesn't seem to compile in 2.0. I haven't spent a lot of time to investigate into running it in 2.0 quite yet.

EDIT: 2.0 does fix it.

[kevcunnane]

We've found an issue using SqlClient with High Sierra. See https://github.com/dotnet/corefx/issues/22453 for the bug report. It's a simple repro and seems like it may be related to the SSL issues you reported to Apple?

[Petermarcu]

At this point we've shipped updates to 1.X and fixed many issues before RTM of 2.0. I'm going to close this now and if anyone finds specific issues on 10.13, please open an issue about it.