I have a WebApp that I debug on MacOS and deliver to the client on Windows. In debug it works great on MacOS, so I created a Web Standalone MacOS Build and ran it, but then it just logs out for no reason:
[ Open.Event Print commands show here OK]
logout
[Process completed]
I tried to connect with the browser to localhost/127.0.0.1 on port 80 and 8080 but nothing. I have Print commands in the App.Open Event that display in Terminal fine. It’s not a timeout issue as it logs out immediately and I have set App.AutoQuit = False. It never gets to the Session.Open Event.
This is getting weirder! I moved the WebApp to a different Mac (running 10.7) and it repeats the error in Terminal about 48 times before the App.Open Event kicks in:
objc[11722]: Object 0x1517390 of class __NSCFNumber autoreleased with no pool in place - just leaking - break on objc_autoreleaseNoPool() to debug
[quote]You may want to start the app with the command line :
./my\ application --port=80 --maxsockets=100
The prompt comes back right away, and then you can access the app with http://127.0.0.1. If you have personal web sharing on, you must choose another port than 80.
[/quote]
Personal web sharing used to be available under the Sharing icon in System Preferences, but I am not sure where it resides now. I have tried port 8000 and it works, so the issue may be due to Apple reserving all lower IP Addresses.
Ports lower than 1024 require elevated permissions, so you’d have to start the standalone web app using the sudo command (also assuming it is not being used by anything else).
