Thank you Svan for your time. I do not take it, or you, for granted
I’ll look into the Terminals shell. So did you launch the app from the Terminal then?
But none of the errors explain the blank screen.
The app is supposed to launch and look like this:
Are you saying that it did launch to this screen for you? Because it never has on the shared executable.
For the dock icon, I used this:
appIcon = loadImage("appIcon.png");
surface.setIcon(appIcon);
(And I put the appIcon.png in the data folder.)
Go into the app bundle and double click on the executable file in the MacOS folder and it opens right up.
The originally exported app does open right up - no need to do anything but double click the main icon.
For the version that is sent over the internet, it does not open right up, unless you change the permissions. And then, it opens to the blank page you experienced.
I simply cannot get this to work right once it’s been sent out. But the same exact exported app folder and executable work flawlessly here until I send it to someone.
So yes, I still thing something is happening to the exported app when it’s being sent to another person, because it WORKS on my computer, and if I send it to myself using WeTransfer it doesn’t work anymore. I did read somewhere that Apple adds some tags or something, but I’m not sure how that’s even possible.
No wonder it doesn’t launch. It’s supposed to look like this:
Before sending it out, it DOES have that exec icon! But it gets changed when sent using a file transfer.
I so appreciate your time Svan. I’m feeling frustrated because I’m no closer to fixing any of the three issues:
- The app not opening at all (and giving the “Application can’t be opened” error)
- After fixing permissions, opening to a blank screen, and,
- Changing the main icon. It never did work using custom application.icns file, despite being listed in the Plist
Do you, or anyone reading this thread, have any ideas how to troubleshoot and solve these problems?
I feel like a lot of this is the kind of behind-the-scenes stuff that Processing should do for the export feature. Why bother giving an export app function if the resultant file does not work when you share it? Authors have little need for an exported app; the main reason to export an app is to share it.
And it simply isn’t working.
Do any processing.org programmers monitor these threads? Maybe I need to reopen or raise this issue again at their gitHub
Thank you so much,
Mike