OK, clyde confirmed this is a GSAK bug, and it will be fixed in the next GSAK build.
So once that build is published and you update to that build, the problem should be fixed.
So once that build is published and you update to that build, the problem should be fixed.
