Closed
Description
@zfi - Building the Mac today app after merging in latest Demo work produces a condition we've seen, and fixed, before...
- when run from the Launchpad, Finder, or Spotlight, the BlocklyPropClient app starts and then immediately stops, producing no GUI or visible error message.
- when run from the console, it indicates that it tried to create a log file inside the Application's bundle... something only su-privileged processes can do:
Jeffs-Mac:BlocklyPropClient.app jmartin$ /Applications/BlocklyPropClient.app/Contents/MacOS/BlocklyPropClient
Traceback (most recent call last):
File "<string>", line 293, in <module>
File "<string>", line 51, in __init__
File "BlocklyLogger.py", line 80, in init
File "logging/__init__.py", line 913, in __init__
File "logging/__init__.py", line 943, in _open
IOError: [Errno 13] Permission denied: '/Applications/BlocklyPropClient.app/BlocklyPropClient.log'
BlocklyPropClient returned -1
This is the behavior, I believe, that was fixed in commit 2848f1cd8, which I verified is in my branch's log history, but I'm now seeing the behavior again.
NOTE: I just managed to get the Mac build to properly generate a modern application bundle format, which equates to two new subfolders in the app's path(bolded below):
- /Applications/BlocklyPropClient.app/ Contents/MacOS/ BlocklyPropClient
Maybe the log file creation is allowed inside the same folder as the actual executable? (see next post) That would be inside the .../Contents/MacOS/ folder.