Hi again, Turns out I was wrong, the call stack from the error gave us an idea about where the error might originate, we have fixed it in that place and hopefully it won't appear that much or at all in the next release. Regards, Lukas
↧