Was this fixed for you in v3.3?