Hello, yes sorry, I just corrected it and I'm starting the build for patching this up.
Have the same issue. I hope the patch will be coming soon and not with the next update in february/march
The 5.2 is already live and fix this issue :)
