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

“flameshot” cannot be opened because the developer cannot be verified #3572

Open
jain6196 opened this issue Apr 17, 2024 · 2 comments
Open
Labels
Unconfirmed Bug The bug is not confirmed by anyone else.

Comments

@jain6196
Copy link

Flameshot Version

All

Installation Type

Linux, MacOS, or Windows Package manager (apt, pacman, eopkg, choco, brew, ...)

Operating System type and version

Apple M3 Pro, macOS Sonoma Version 14.3

Description

I am unable to install flameshot in mac as I am getting this issue as "macOS cannot verify that this app is free from malware"
Is there any way that I can do that.

image

Steps to reproduce

Download flameshot.dmg and double click to install

Screenshots or screen recordings

image

System Information

Apple M3 Pro, macOS Sonoma Version 14.3

@jain6196 jain6196 added the Unconfirmed Bug The bug is not confirmed by anyone else. label Apr 17, 2024
@HeinanCA
Copy link

Occurs to me as well on M3 Pro, macOS Sonoma v14.4.1

@ObjectOrientedGuy
Copy link

check this section in README.md file

Note that because of macOS security features, you may not be able to open flameshot when installed using brew. If you see the message “flameshot” cannot be opened because the developer cannot be verified. you will need to follow the steps below:

  1. Go to the Applications folder (Finder > Go > Applications, or Shift+Command+A)
  2. Right-Click on "flameshot.app" and choose "Open" from the context menu
  3. In the dialog click "Open"

After following all those steps above, flameshot will open without problems in your Mac.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Unconfirmed Bug The bug is not confirmed by anyone else.
Projects
None yet
Development

No branches or pull requests

3 participants