This is a known issue and we're already working to fix it, so stay tuned for updates!