# Exported app not working macOS

**URL:** <https://discourse.processing.org/t/exported-app-not-working-macos/8501>\
**Category:** Libraries\
**Created:** [February 18, 2019, 9:50am UTC](https://discourse.processing.org/t/exported-app-not-working-macos/8501 "2019-02-18T09:50:55Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![tobeheard](https://avatars.discourse-cdn.com/v4/letter/t/65b543/32.png) [@tobeheard](https://discourse.processing.org/u/tobeheard)\
**Post date:** [February 18, 2019, 9:50am UTC](https://discourse.processing.org/t/exported-app-not-working-macos/8501/1 "2019-02-18T09:50:55Z")

</div>

Hello and thank you community, I have a problem with my exported app. It does not open. I’ve tried the control open and double click. They both flash the icon, yet nothing happens.  
my code is using the following libraries

import processing.pdf._;  
import java.util.Calendar;  
import processing.video._;  
//import processing.sound.\*;  
I have tried with the sound parts disabled as I have a 20min wav file that plays but to no avail.

my data is in the java folder in package contents  
I have 2 .txt files and a .wav file

code runs fine in processing 3.5.3  
my mac os 10.12.6  
have not tested on windows as I have no PC

what code would be helpful for anyone to help solve this puzzle?

thank you, my first post here.

---

<div class="post-metadata">

**Author:** ![LangdonS](https://avatars.discourse-cdn.com/v4/letter/l/ebca7d/32.png) [@LangdonS](https://discourse.processing.org/u/LangdonS)\
**Post date:** [January 9, 2023, 3:52pm UTC](https://discourse.processing.org/t/exported-app-not-working-macos/8501/3 "2023-01-09T15:52:38Z")

</div>

I have the exact same problem!  
The exported app is just a dead light grey window.  
I cannot download Processing 4 as I am using MacOS 10.13.6.

---

<div class="post-metadata">

**Author:** ![LangdonS](https://avatars.discourse-cdn.com/v4/letter/l/ebca7d/32.png) [@LangdonS](https://discourse.processing.org/u/LangdonS)\
**Post date:** [January 9, 2023, 3:53pm UTC](https://discourse.processing.org/t/exported-app-not-working-macos/8501/4 "2023-01-09T15:53:30Z")

</div>

I am working on a Pac-Man game  
www.getpacman.gq

---

<div class="post-metadata">

**Author:** ![quark](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.processing.org/quark/32/26_2.png) [@quark](https://discourse.processing.org/u/quark)\
**Post date:** [January 9, 2023, 4:10pm UTC](https://discourse.processing.org/t/exported-app-not-working-macos/8501/5 "2023-01-09T16:10:24Z")

</div>

I don’t know if this is your problem but all resource files e.g. images, sounds, text files must be in the sketch’s data folder when exporting the app otherwise they will not be included in the export.

---

<div class="post-metadata">

**Author:** ![LangdonS](https://avatars.discourse-cdn.com/v4/letter/l/ebca7d/32.png) [@LangdonS](https://discourse.processing.org/u/LangdonS)\
**Post date:** [January 9, 2023, 5:03pm UTC](https://discourse.processing.org/t/exported-app-not-working-macos/8501/6 "2023-01-09T17:03:26Z")

</div>

they are definitely there. It runs if you right click the .app, navigate to the MacOS folder, and click the file within. I have recently discovered that Gatekeeoper is indeed the culprit. For some strange reason, clicking on “Run Anyway” in “System preferences” runs the app but breaks it. You either have to destroy Gatekeeper with `sudo spctl --master-disable` or use the “show contents” solution.

---

<div class="post-metadata">

**Author:** ![FSXAC](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.processing.org/fsxac/32/3995_2.png) [@FSXAC](https://discourse.processing.org/u/FSXAC)\
**Post date:** [January 10, 2023, 4:48pm UTC](https://discourse.processing.org/t/exported-app-not-working-macos/8501/7 "2023-01-10T16:48:44Z")

</div>

If you’re exporting the app to use locally by yourself, I think opening from the right-click menu a couple times seems to work for me. [See more here](https://support.apple.com/en-ca/guide/mac-help/mh40616/mac). You may need to also tinker with [System Preferences](https://www.lifewire.com/fix-developer-cannot-be-verified-error-5183898) as well.

If you’re exporting the app to use on other computers or for other people on newer versions of macOS, you need to have the app _signed and notarized_ for security. In that case there is no easy way around except registering to become an Apple Developer and paying $99/year so that you can generate certificates for your apps.