I got a similar report about this issue today. Perhaps it is a time-based one (expired code-signing certificate used in 1.1?)
I will be releasing Nimble Kick 1.2 soon with a bunch of improvements. Perhaps that will solve your problem too if you haven't figured it out by then.