The fix was actually reverted in the 1.0.9 package due to a situation where a server error could occur (with older reports). If you redownload 1.0.9, it should "fix" the issue (which is really just a restoration back to the version before, which did have the named bug).