-
Notifications
You must be signed in to change notification settings - Fork 76
Plugins don't update in sandbox containers #14
Comments
I'm aware of this issue while creating other SIMBL plugins. For resolving this issue manually, please try following:
As far as I know, sandbox will not allow accessing symbolic link content from inside of container to outside of container. |
Hmm.. I happened to be developing a plugin when I noticed this, so I guess it's possible that it only happens then. If you look at the actual contents of the Container, you'll notice most of the folders are actually symbolic links. For example:
|
I recognized those symbolic links are specially permitted. On releasing EasySIMBL-1.0, I selected creating hard link of I noticed this issue when developing SyncTwitterClient. |
Hello Nomura-san Thank you for EasySIMBL! it is great! (I check/uncheck the "Use SIMBL" check box to restart the agent so the new version of my plugin is used) |
I have stopped developing my SIMBL plugins since I stopped using Twitter for Mac which was major reason for developing plugins. I may have to create some plugins after Yosemite will be released, but I can't say I will see this issue again. |
I see, thanks for letting us know. :) |
I just released EasySIMBL-1.7.1 containing 524be0c which make more stable detecting termination of sandboxed applications. |
So I'm not sure if I'm doing something wrong, but I've noticed that if I install a plugin in
~/Library/Application Support/SIMBL/Plugins
and start a sandboxed app that uses it, any updates made to a plugin won't be copied to the sandbox until deleted from the container folder. I fixed this by making the SIMBL folder in the container a symbolic link to the normal SIMBL folder, but I'm not sure where to even begin implementing this in the code.This is the command I ran in terminal:
The text was updated successfully, but these errors were encountered: