[BUG] Pearcleaner immediately exits when launched from Raycast or open, but works from Finder #589

Pearcleaner immediately exits when launched from Raycast. It works normally when double-clicked directly from the /Applications folder in Finder.

The issue still occurs after reinstalling Pearcleaner:

brew reinstall --cask pearcleaner

Environment

• Pearcleaner: 5.4.3 (build 121)
• Raycast: 1.104.23
• macOS: 26.5.2 (build 25F84)
• Architecture: Apple Silicon / arm64
• Installation: Homebrew Cask
• App path: /Applications/Pearcleaner.app

Steps to reproduce

1. Open Raycast.
2. Search for Pearcleaner.
3. Press Enter.
4. Pearcleaner appears briefly and immediately exits.

The issue can also be reproduced without Raycast:

/usr/bin/open -a /Applications/Pearcleaner.app

However, double-clicking /Applications/Pearcleaner.app directly in Finder opens it normally.

Expected behavior

Pearcleaner should remain open regardless of whether it is launched from Finder, Raycast, or the open command.

Actual behavior

When launched from Raycast or with open, Pearcleaner exits approximately 0.6 seconds after launch. No crash report is created in ~/Library/Logs/DiagnosticReports.

The unified log reports a normal exit:

launchd: service inactive: application.com.alienator88.Pearcleaner...
runningboardd: termination reported by launchd (0, 0, 0)

The log also contains this message while Pearcleaner checks its Finder extension:

Prompting policy for hardened runtime; service: kTCCServiceAppleEvents requires entitlement com.apple.security.automation.apple-events but it is missing

It references com.alienator88.Pearcleaner.FinderOpen. This warning may be related to the early exit, although I cannot confirm causality.

Code-signing diagnostics

After a clean Homebrew reinstall:

codesign --verify --deep --strict --verbose=4 /Applications/Pearcleaner.app

returns:

/Applications/Pearcleaner.app: invalid signature (code or signature have been modified)
In architecture: arm64

spctl returns:

/Applications/Pearcleaner.app: internal error in Code Signing subsystem

Additional information

• Reinstalling the Homebrew cask did not resolve the issue.
• Only one Pearcleaner installation exists.
• No conventional crash report is generated.
• The problem appears to depend on the launch context.