We are working on an update that will resolve that error. You can read more about that issue earlier in this thread, as well as here in the Technical Issues forum.