As I said:
That's still true.
The fix will be in 10.0.3.1 beta (which we haven't released yet) and was never going to be part of 10.0.3.0 (which we released yesterday).
As I said:
That's still true.
The fix will be in 10.0.3.1 beta (which we haven't released yet) and was never going to be part of 10.0.3.0 (which we released yesterday).