I've encountered exactly the same problem. I was able to fix the problem by setting the provisioning profile to something other than Automatic on both targets (the test and the test host).
I verified this was the problem by reverting it back to automatic, and the problem reoccured.