# 4.4.4 runs ok from command line, but not as app

**URL:** https://discourse.processing.org/t/4-4-4-runs-ok-from-command-line-but-not-as-app/46646
**Category:** Processing
**Created:** [July 2, 2025, 5:08am UTC](https://discourse.processing.org/t/4-4-4-runs-ok-from-command-line-but-not-as-app/46646 "2025-07-02T05:08:21Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![sableraph](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.processing.org/sableraph/32/251_2.png) [@sableraph](https://discourse.processing.org/u/sableraph)
#### Post date: [July 2, 2025, 12:50pm UTC](https://discourse.processing.org/t/4-4-4-runs-ok-from-command-line-but-not-as-app/46646/4 "2025-07-02T12:50:55Z")

</div>

Hi @toby,

That’s very strange and I can’t reproduce the issue on my MacBook Pro running 15.5.

Each release of Processing is code signed and notarized, so it shouldn’t be quarantined. And as you said, macOS would normally display an alert if that were the case.

Could you try [Processing 4.3](https://github.com/processing/processing4/releases/tag/processing-1293-4.3) and [Processing 4.3.1](https://github.com/processing/processing4/releases/tag/processing-1294-4.3.1) and let us know if the same issue occurs with those versions?

For accurate results, make sure to close all running instances of Processing before opening a different version.

Is there any additional info you could share about your setup? Anything out of the ordinary that might help us narrow it down?

---

_[View the full topic](https://discourse.processing.org/t/4-4-4-runs-ok-from-command-line-but-not-as-app/46646)._