If StateChangeAction path contains a space, the script will not trigger

Log error:

NoMAD[3265:45970] launch path not accessible

added Bug label

changed milestone to %v. 1.0.3

If you escape the spaces with a \ does it work?

Here's what I found after some more experimentation:

defaults write com.trusourcelabs.NoMAD StateChangeAction /Users/jcuozzo/OneDrive\ -\ Company/Scripts/script.sh

doesn't work.

defaults write com.trusourcelabs.NoMAD StateChangeAction "/Users/jcuozzo/OneDrive\ -\ Company/Scripts/script.sh"

doesn't work.

defaults write com.trusourcelabs.NoMAD StateChangeAction -string "/Users/jcuozzo/OneDrive\ -\ Company/Scripts/script.sh"

works! I will leave it up to you whether this should stay open, but I'm happy with the workaround.

Thanks for this great tool BTW!

added Documentation and removed Bug labels

This is similar to how you need to do path strings for other actions.

Glad you have it working, I'll keep this open to remind me to add this to do the docs.

Preference key documentation updated.

https://www.nomad.menu/help-center/preferences-and-what-they-do/

closed