I will investigate this in more detail for sure for the upcoming release. We are moving to a different solution either way, that will probably circumvent this issue alltogether.
Either way, they are probably will fix this sooner or later for sure. I don’t think those are related issues, but it is possible. I definitely need to investigate this further, to make sure I am not doing something incorrectly. From what it looks like, the issue is probably on their side.