We are also affected by this. The exception in question is thrown from a third-party library, so we cannot really fix it on that end.