Thanks for the reports! This is a known issue and we're working to address this in a future update.