The version is 3.0.2, but I heard this issue was already fixed in a 2.x.x release—is that not the case?