We're sorry that this happened. We're working on fixing it as soon as possible.
The 1.0.1.0 update on the demo appears to have fixed the problem.
