Search:

After a second check, we are now confident that the issue is the same that was fixed in version 4.1.2 of the library.
Hence, the upgrade to at least 4.1.2 is the way to proceed. Unfortunately, I...

We had no report of a similar issue on that version, so the case should be investigated in the details.
However, to do this, you should upgrade further to the latest version of the library.
You can...