This bug is fixed since v2.0.0, no cookie clearing required
This version is currently in beta, read more here: