I will check and guess I will have fixed it already for the service update 1.0.1 end of July.
If I find any workaround earlier, I let you know.
I will check and guess I will have fixed it already for the service update 1.0.1 end of July.
If I find any workaround earlier, I let you know.