Tag Archives: application

Invalidating Preferences Cache in Mavericks (OS X 10.9.x)

I recently set up a fresh install of Mavericks (OS X 10.9), and copied over some of preferences (plist) files from old installation to new box (Ā (~/Library/Preferences).

I noticed, applications failed to use (manually copied) preferences files, instead kept throwing errors (like one shown below):

cfprefsd[xxxx]: CFPreferences: error renaming file /Users/username/Library/Preferences/com.codeux.irc.textual.plist.bPsEnTV to /Users/username/Library/Preferences/com.codeux.irc.textual.plist

Unlike previous versions of OS X, Mavericks (OS X 10.9) caches preferences files. That means, if we edit or overwrite a preferences (plist) file, we need to invalidate the cache so that applications can see the changes, and start using this updated preferences file.

I didn’t want to set up everything from scratch, in this case all IRC servers, nodes and chatrooms. It is not fun editing binary plist files, even with the help of XCode šŸ™‚

To fix this problem, we need to run this from terminal:

defaults read ~/Library/Preferences/com.codeux.irc.textual

We also need to make sure preferences file has correct permission. In my case, permissions were messed up because I copied file from different disk (installation).

Permission should look like following (i.e. owner can at least read/write; umask 077):


I would suggest restarting the respective application, if it is already running.

A Developer’s Open Letter to RIM

Jamie Murai has written an open letter to RIM, the company behind Blackberry and Playbook. Jamie talks about his experience of setting up development environment for Playbook application development.

It seems, RIM has failed to attract developers, the credit goes to broken development process and tool-chain. One has to spend good amount of time (and money?) setting up development environment, building application and deploying the same to marketplaces.

Why would developers bother looking at Playbook development, when they have better options (iOS and Google Android), where Ā development, deployment and monetization is relatively very-very simpler.

Developer usability is very important. Any company that relies on developer community/ecosystem for their growth, should take some lessons from Jamie Murai’s open-letter, which enlists some important points/issues.

Read Jamie Murai’sĀ Open Letter To RIM’s Developer Relations.