Thank you so much for reporting this issue! I have fixed it on develop, so the next build will include this fix.