Issue #70 for this package has popped up unexpectedly. It persists even after the current 1.2.3 update. Is there a proposed resolution to the bug?
Since it is unlikely that you’ll get a response from the author of the package here (given that they haven’t responded on their own repo), if you’re looking to get help from random community members, can you specify what the actual issue is? This saves everyone the time of having to manually go find the link to the issue and then try to figure out what it is you’re asking.