You might double check to make sure there aren't any other issues. I was using v1.10.2 when I had
this issue happen last week.
I switched back to 1.7.2 since my application was still compatible with it.
However - I'm going to take a look at the link FroggEye posted for future sites. Ha, where was that suggestion last week? :D