This is known issue and cannot be fixed on the extension side. A workaround of this issue will be available in the next release.