Yes, this is a known issue, and it has already been fixed in version 0.5.6. But thank you anyway for your concern and help
