1.6 is roughly beginning of February, so it's very, very old. The issue may have very well been resolved. It has, after all, been 6 months of updates you're missing out on.
My suggestion is update before I push 2.1.0, as I've removed some long-deprecated functionality which will break some things when you update such an old project. The backwards compatibility code is still present in the current version (2.0.9).