Skip to content
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

Malicious software #234

Open
alemputes opened this issue Mar 21, 2021 · 3 comments
Open

Malicious software #234

alemputes opened this issue Mar 21, 2021 · 3 comments

Comments

@alemputes
Copy link

What is the issue
Trying to run the application but getting the following:
“Swimat” can’t be opened because Apple cannot check it for malicious software.

Expected behavior
Needs to be updated to run properly?

Desktop (please complete the following information):

  • OS: [e.g. 10.14, 10.15]
  • 11.2.3
  • App Version [e.g. 1.6.2]
  • 1.7

Additional context
Add any other context about the problem here.

@Jintin
Copy link
Owner

Jintin commented Mar 22, 2021

Not sure what is the required steps to get rid of this.
Do we need to publish via Mac App store or change any certificate or build process? @saagarjha

And found an article about this, is this help? @alemputes
https://support.postbox-inc.com/hc/en-us/articles/360041824214-Error-Postbox-can-t-be-opened-because-Apple-cannot-check-it-for-malicious-software-

@alemputes
Copy link
Author

alemputes commented Apr 3, 2021

I would recommend to publish it to the app store as this will get you more exposure and users will feel more safe using it. Even thought there might me workarounds to install Swimat, many users may not go thru that trouble to find a solution for it and the warning that pops up could also scare some.

@saagarjha
Copy link
Collaborator

I think this is more a problem with "this Mac can't connect to Apple's servers to verify notarization" and less "we are signing Swimat incorrectly".

Getting Swimat on the App Store is possible and maybe even desirable, but it would require a bit of work. At the very least, the command line tool would need changes due to sandboxing requirements.

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

No branches or pull requests

3 participants