Restarting and re-installing is not the solution. As stated the software/process works perfectly fine while in the Admin Account, but not within the Managed Account. It appeared to only be the upload to Adruino process which was hindered. Everything else appeared to work fine.
Here is what I did to solve the issue. 1 - I noticed that the upload process seams to call another program to run. This program did not reside within the main Applications folder on the Mac. 2 - I figured there was some sort of permissions thing hindering the second app from running, even though I had given specific permission to the MBlock app to run in the managed account.
I found this site:
http://switchtoamac.com/guides/applications/application-contents.html
and
https://support.apple.com/kb/PH25287?locale=en_US
These allowed me how to look through the MBlock application contents/files. Using the “get Info” menu (right click on a file name, select get info from the pop up menu), I discovered the managed account had specific read/write permission for the executable. In that folder structure I found the MBlock executable (contents/MacOS/mBlock) by looking for a black icon with tiny word “exec” in it.
I also dug around some more and found the application which is launched during file upload process /Contents/Resources/Arduino/Arduino.app. This is another packaged application, so right clicking and selecting show contents allowed me to browse it as well. All files within this application were included in the Admin Account and Everyone group, but not the Managed account.
I used the process described in the second site and gave every file and folder specific read/write access to the managed account. I did this in the Arduino.app package and the mblock.app contents folders.
Everything now works in both accounts. I’ll post back if further issues come up.
Bottom line is that this should have worked on it’s own without me having to take multiple evenings to figure it out. Other applications can do this just fine. I’m curious if this was a thought within the development process. And I hope I don’t have jump through these hoops again when the next version of mBlock comes out.
@tec_support Would it have worked to include Arduino.app as a program in the Applications main folder rather then burying it? I’m curious if this would force the “enter admin user/password to allow it to run” pop up window when it gets called from mBlock in a Managed Account. I’m curious if with it buried like it is, the MacOS thinks it already asked the question. At the least it would allow for users to assign it permission via the parental controls section of the System Preferences application.
I’m sure I’m not the only one that doesn’t want to give full Admin privileges to a 10 year old.
