WorkingDirectory not supported if it CONTAINS $APP_PACKAGE as part of a path #12
Comments
|
I just ran into the same problem. I fixed it thus: Change
To
Where 12 is the length of $APP_PACKAGE and do similar for the other cases where lengths will differ. |
|
That's an even more elegant solution than mine, I had forgotten about bash substring capabilities |
|
While the bash substring solution still is a very nice idea to solve this issue, I'll stick to the same solution as for the |
|
That works too, I hadn't even considered it since I'm really a Linux guy and I'm never quite sure exactly what will work on a Mac without doing extensive testing :D I didn't have time to do extensive testing when I hacked the script. I needed it to work "now", as they say. |
This is our WorkingDirectory key/val pair from our plist
WorkingDirectory
$APP_PACKAGE/../
The$APP_PACKAGE never gets correctly replaced with $ {AppPackageFolder}
I would assume the same is true for all of the entries that check for equality instead of contains, and should probably do a contains check with a replace instead of an equality and a set.
I hope that's clear, I'm rambling a bit today. Mostly because I can't get my thoughts into any type of clear and concise order.
I assume some trick with sed would work, but I'm not very good with sed, so my hackish attempt is thus
elif [[ "${JVMWorkDir}" =~ "$APP_PACKAGE" ]]; then
WorkingDirectory="${AppPackageFolder}"$(sed 's|$APP_PACKAGE||g' <<< ${JVMWorkDir})
And... seems to work. At least, I can enter the app and manually run the script and it works. Or I can do open App.app from the command line and it works. However, trying to double click the app to have it work from the GUI still fails.
The text was updated successfully, but these errors were encountered: