I agree. I have opened a related bug on the github repo and hope to resolve it soon.

update: Please try out the updated version 3.3 and let me know if the issue still persists.