This is a known issue and has recently been fixed in the development branch as described in this thread.