This worked for us as a workaround until we we find the true solution to the issue.

Can confirm workaround still works.

@rio you are a bit of a genius. This works as a workaround until we have a proper fix. I still think it has to do with some async stuff we do in our app.

Can you tell me where to find this reports. So I don't have to ask next time? :-)