macOS 'App Not Verified' Error: How to Bypass and Fix

What the "App Is Not Verified" Error Means

The "App Is Not Verified" error (also known as "unidentified developer" or "app is not verified") is a standard macOS security warning that appears when you try to run an application not signed with a digital signature from a developer registered in the Apple Developer Program.

The system dialog typically looks like this:

"App Name" can't be opened because Apple cannot verify it doesn't contain malicious software.

The error occurs not because of problems with the app itself, but due to the policies of the built-in protection system Gatekeeper. Gatekeeper checks whether an app is signed with an Apple Developer ID certificate and whether it is intact. If the check fails, macOS blocks the launch.

Causes

1. Missing Apple Developer ID digital signature. The developer has not paid for a subscription in the Apple Developer Program (~99 USD/year) and has not signed the app. This is common for small studios, hobby projects, or internally used software.
2. Corrupted signature or file. The app file was modified after signing (e.g., a plugin or mod was added), or the archive was unpacked incorrectly, breaking the checksums.
3. Downloaded from an untrusted source. The app was downloaded from a file-sharing site, a piracy website, or via torrent, where it could have been modified.
4. Quarantine attribute (com.apple.quarantine). macOS automatically marks files downloaded from the internet (via browser, email) with this attribute. On first launch, the system checks it via Gatekeeper. If the app is unsigned, Gatekeeper blocks it.
5. Expired or revoked signature. The developer's certificate has expired or been revoked by Apple (e.g., for violating rules). In this case, even a signed app may be blocked.

Solutions

Method 1: Run via Finder (Safest and Simplest)

This method uses macOS's built-in mechanism to allow a specific unsigned app to run just once.

1. Locate the app file (usually a .app in the Downloads or Applications folder) in Finder.
2. Do not double-click it. Instead, hold down the Ctrl (or Cmd) key and left-click the app icon.
3. In the dropdown menu, select "Open".
4. A warning dialog will appear, but instead of an "OK" button, there will be an "Open" button. Click it.
5. macOS will remember this decision for this specific app and will allow you to launch it with a double-click next time.

💡 Tip: This method only works for apps that have not been modified since download and have a correct .app bundle structure.

Method 2: Remove the Quarantine Attribute via Terminal

If the app was downloaded but Finder doesn't offer the "Open" button (or you prefer working in the terminal), you can manually remove the quarantine flag.

1. Open Terminal (Applications → Utilities → Terminal).
2. Determine the full path to the app. The easiest way: drag the .app file icon from Finder directly into the Terminal window—the path will paste automatically.
3. Enter the command, replacing /full/path/to/app.app with your actual path:

   xattr -d com.apple.quarantine /full/path/to/app.app
   

   Example: xattr -d com.apple.quarantine /Users/username/Downloads/MyApp.app
4. Press Enter. If the command runs without errors, the attribute is removed.
5. Now try to launch the app with a normal double-click.

⚠️ Important: This command only removes the quarantine attribute. It does not disable Gatekeeper globally and does not remove other potential security attributes.

Method 3: Change Security Settings in System Settings

macOS allows temporarily allowing apps from "unidentified developers" system-wide, but only for a specific case where the app has already been blocked and the system has offered this action.

1. Try to launch the app with a double-click. A dialog about the error should appear.
2. Go to "System Settings" → "Privacy & Security".
3. Scroll down to the "Security" section.
4. If macOS has detected an attempt to run a blocked app, a message and an "Allow" button will appear at the bottom of this section.
5. Click "Allow". The app will then be launchable.

⚠️ Limitation: This method works only if the system has already recorded a launch attempt. If you've just downloaded the file and haven't tried to open it yet, the "Allow" button won't be there.

Method 4: Completely Disabling Gatekeeper (Not Recommended)

This is an extreme measure that significantly reduces your system's security by allowing any software to run without verification. Use only if you are absolutely sure about the app's source and understand the risks.

1. Open Terminal.
2. Enter the command:

   sudo spctl --master-disable
   

3. Enter your administrator password (characters won't be displayed).
4. After this, in the security settings (System Settings → Privacy & Security), a toggle for "App Store" and "App Store and identified developers" will appear, along with a new option "Anywhere". Select "Anywhere".
5. Now macOS will not verify signatures at all.

To restore protection, run in Terminal:

sudo spctl --master-enable

Prevention

1. Download only from official websites. Avoid file-sharing sites and "cracked" (piracy) versions. Official websites either sign their apps or use common installer formats (.pkg, .dmg with a valid signature).
2. Verify SHA checksums. Reliable developers often publish hashes (SHA-256) of their archives. Compare the hash of your downloaded file with the one on the website. If they don't match—the file was modified.
3. Use antivirus software. Even on macOS, scanners (like Malwarebytes, ClamXAV) can detect modified malware disguised as legitimate software.
4. Don't disable Gatekeeper permanently. Use Method 2 (xattr) for targeted permission for trusted but unsigned tools (e.g., utilities from enthusiasts). This maintains overall system protection.
5. Update macOS. Every system update improves Gatekeeper's algorithms and threat databases.

Frequently Asked Additional Questions

Can I remove the com.apple.quarantine attribute for the entire "Downloads" folder at once? Yes, the command xattr -d com.apple.quarantine ~/Downloads/* will remove the attribute from all files in the folder. Do not do this routinely! This disables checking for all downloaded files, including potentially dangerous ones. Use it only for a specific, known .app file.

The app still doesn't launch after removing the attribute; the error is different. The app might be genuinely corrupted or require third-party libraries (e.g., .NET Framework, Java). Check the system requirements on the developer's website. The error could also be related to missing execute permissions (chmod +x).

Why does the app still not launch even after "Allow" in security settings? The system might have blocked the app for another reason: for example, it requires outdated kernel extensions (KExt) or was signed but the developer's certificate was revoked. In this case, only Method 2 or contacting the developer for an updated version will help.

Can I automate the process for multiple apps? Yes, you can create a simple Bash script:

#!/bin/bash
# Usage: ./unquarantine.sh /path/to/app1.app /path/to/app2.app
for app in "$@"; do
    if [[ -d "$app" ]]; then
        xattr -d com.apple.quarantine "$app" 2>/dev/null
        echo "Quarantine attribute removed for: $app"
    else
        echo "File not found: $app"
    fi
done

Save as unquarantine.sh, give it permissions with chmod +x unquarantine.sh, and run it with paths to your apps.

What if the app requires "Full Disk Access"? After a successful launch, some utilities (e.g., for system cleaning or monitoring) may request additional permissions. Go to System Settings → Privacy & Security → Full Disk Access and add the app to the list. This is a different setting, not directly related to Gatekeeper.