@meierjan thank you for your contribution. We have now released version 0.1.4 which is using the latest version of the support libraries, so you shouldn't see this issue again. As an additional note ...