Having been alerted that Apple have some strict (new?) guidelines on the folders that an app is allowed to use for storing its properties, I've had to have a bit of a shake-up of the PropertiesFile class.
Since it was impossible to fix these paths without breaking user-code (or causing silent failures), I've taken the opportunity to have a bit of a clear-up in the PropertiesFile class. I've refactored all of its options into a structure now, which is also used in the ApplicationProperties class, and this has eliminated quite a bit of messy/repeated code. The structure contains a value osxLibrarySubFolder which helps sort out the OSX location problem - see its comments for more details.
This does mean that you'll need to rewrite any code that used PropertiesFile::createDefaultAppPropertiesFile() or ApplicationProperties::setStorageParameters(), but should be pretty straightforward, and leads to more readable code.
For a good example of how to rewrite this stuff, have a look in the Introjucer/Utility/StoredSettings.cpp, inside the StoredSettings::flush() method, where it also shows how to migrate an old preferences file to a new location without losing any settings.
Also as part of these OSX file location changes, I've had to tweak the InterprocessLock behaviour, to put its locking files into /var/tmp rather than the Library/Juce folder that it used to use, which is apparently now verboten. If you have an app which needs to use an interprocess lock, you'll need to make sure that all the apps are built from the latest version of the codebase, so that they're all looking in the same folder for their locking files.