correct this issue is in the migration guide so if you upgrade and follow the migration staps this issue would be fixed