Basically no, it hasn’t been fixed with 4.12.2.
We both tested on 4.12.2 and it didn’t worked, also tested on this build and the internal build. And both of them failed hard.
Basically no, it hasn’t been fixed with 4.12.2.
We both tested on 4.12.2 and it didn’t worked, also tested on this build and the internal build. And both of them failed hard.