-
Notifications
You must be signed in to change notification settings - Fork 353
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing Notarization - Fails to run on recent MacOS #123
Comments
Investigation: This appears related to .NET core including versions 2.1, 3.0 and 3.1 and is discussed in several .Net Core issues all linking to the same FAQ and promise to address over the next few months. The .Net team is working with Apple to address it. "macOS Catalina introduced new security features which affect the .NET Core installers. If you run the installer after downloading using a web browser, a warning dialog will open stating the package "...can't be opened because Apple cannot check it for malicious software.", and the installation will be stopped. To override this behavior, go to Settings : Security & Privacy and choose "Open Anyway" next to the dotnet installer text. We are working to update our installers for the new Catalina requirements. These will be released during an upcoming monthly update." -see https://github.com/dotnet/core/blob/master/release-notes/3.1/3.1-known-issues.md#net-core-installation-on-macos-catalina-1015 |
Investigation: issue extends beyond .net apps. https://www.cultofmac.com/672576/cant-launch-your-apps-on-macos-catalina-heres-the-fix/ |
Again, this appears to be a general .Net Core issue that Microsoft is working on as mentioned earlier and not specific to this application. See the .Net core release document link above for more including details of how to resolve for now. |
Describe the bug
Reported via Hacker News, and similar to Microsoft/ApplicationInspector#341, we're going to need to get binaries distributed for MacOS notarized if they're going to run there.
To Reproduce
TBD, we'll test this out later this week. It's possible that "dotnet ApplicationInspector.dll" might work, assuming the .NET Core runner is notatized.
Expected behavior
The application should run normally.
Screenshots
n/a
Desktop (please complete the following information):
Smartphone (please complete the following information):
n/a
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: