Thank you for reporting.
We have managed to reproduce the issue on our side and the fix will be ready in the next minor release 2.414 (ETA Feb 12).
Does it work for you?
We are using licensekey instead of licenseFilePath now and it is working.
We are glad to inform you that the version 2.414 is already available on our website.
You are welcome to update the component.