11-11-2020, 08:51 PM
I figured the issue was around the init code. Code should work reliably every time. The reason for it working after adding a dialog is uncertain. I have some other thoughts that may or may not be of any use.
Are you running on Mac Catalina or Big Sur? Apple Notarization may be a factor.
You can see that we are accounting for that in the LCM startup with specialFolderPath("support"). Our startup code will not work well in standalones on systems running Mac 10.14 or newer. The best we can do is document how to modify the path to work with how people will deal with notarization. The database needs write permission. Mac developers will need to store their database outside of their standalone going forward. We chose to store our data in the 'Application Support'.
Are you running on Mac Catalina or Big Sur? Apple Notarization may be a factor.
Code:
case "MacOS"
put specialFolderPath("support") into tLibraryPath
put "/" & "CanelaSoftware/" & gCSManifestA["productName"] & "/" & gCSManifestA["productVersion"] & "/data" after tLibraryPath --LCM SPECIFIC PATH
breakYou can see that we are accounting for that in the LCM startup with specialFolderPath("support"). Our startup code will not work well in standalones on systems running Mac 10.14 or newer. The best we can do is document how to modify the path to work with how people will deal with notarization. The database needs write permission. Mac developers will need to store their database outside of their standalone going forward. We chose to store our data in the 'Application Support'.