Hi, I believe the issue you described has been fixed in the latest version (7.0.0). Since you're currently using it, everything appears to be working flawlessly on our end. Could you please share more details via the contact email?