hey there! we recently deployed a fix for this - can you try uninstalling and reinstalling the extension?