Completely forgot about this post…
We are still facing this issue with 2.1.0p14. So this seems not to be an issue with 2.0 specifically.
Completely forgot about this post…
We are still facing this issue with 2.1.0p14. So this seems not to be an issue with 2.0 specifically.