Not getting this bug anymore in 1.2.0 build 3, fwiw.
Its maybe 1/20 times it's happened not consistently recreatable
Please Login to reply.
No replies yet.
