CoreTend

SUPPORT Diagnostics

Resolve issues without weakening macOS.

CoreTend 0.9.1-rc.5 has no Developer ID signature and is not notarized. The first Gatekeeper block is expected, not an application crash.

Version 0.9.1-rc.5macOS 14.0+arm64

01 / Path

Three checks before reporting a problem.

Every step keeps macOS protections enabled.

  1. Verify the download

    Compare its SHA-256 with the checksum file published beside the DMG.

    Provenance

  2. Open it once

    Copy CoreTend to Applications and double-click it. The initial block makes the next system option available.

    Expected

  3. Allow this copy

    System Settings → Privacy & Security → Open Anyway. Never disable Gatekeeper globally.

    Once

02 / Details

A technical block ready to attach.

It contains no personal path or scan data.

CoreTend 0.9.1-rc.5
CoreTend-0.9.1-rc.5-arm64-unsigned.dmg
minimum macOS: 14.0
architecture: arm64
Developer ID: no
notarized: no
SHA-256: b654975770cc1bfeb7e6a4f3cf180653a3182a55f8dc135db2083a72528998eb
The app does not open after download

Verify the checksum, try opening once, then use Open Anyway in Privacy & Security. The expected rejection of an unnotarized build is not the same as a crash.

A scan cannot see some folders

Review exclusions and Full Disk Access. Grant only the permission required by the workflow you are using.

What should a report include?

The version, macOS release, architecture, affected module and reproducible steps. Remove personal file names from every screenshot.