I don't know what you mean by "you have to link the Script Libraries folder as you do in the first place". I'm using a symlink in the normal, typical manner.
Just to be clear, here's my setup:
In my ~/Library folder, I have a symlink named "Script Libraries":
The symlink points to a normal folder in my DropBox Setup, named "Script Libraries":
The "Script Libraries" Symlink
IAC, I've done enough tests now to convince myself that the issue is caused by a framework being in the script lib package, when the package is in a folder synced by Dropbox.
- This fails consistently: using the SQLite Lib.scptd when that package is in a folder synced by Dropbox
- Each of These Work consistently:
- Pause the DropBox sync service, and use SQLite Lib.scptd in the symlinked folder.
- Put the SQLite Lib.scptd in the normal non-symlinked, ~/Library/Script Libraries folder
- Remove the FMDBAS.framework package from SQLite Lib.scptd, and put it in ~/Library/Frameworks, but keep SQLite Lib.scptd in the symlinked Dropbox folder
I don't understand this. The ONLY folder DropBox is syncing is the "Script Libraries" folder here:
It is NOT syncing the symlink to this folder.
This is the ONLY issue I have had with DropBox over the many years I've been using it. I have a whole set of folders in the DropBox sync path that I have either symlinks or aliases (all outside of the sync path) that point to these folders. Until now, this has allowed me to keep all of my Macs in sync with virtually no effort or issues.
Thanks for your help in trying to resolve this issue.