I have not seen this error with 2.2.0. I suspect that the behavior was fixed as part of another bug fix.
I have not seen this error with 2.2.0. I suspect that the behavior was fixed as part of another bug fix.