Just had a reply from support....

The developers are aware of this issue and are working to resolve it in the next build update.

So it looks like it is a bug

Regards