This message was deleted.

Why not fix it on the SDK side to force the Attribute into a more consistent state?

I'm hoping to minimise the dev effort required (and some of our older customers won't hit the screens that set the attribute until they've updated the app). Does this mean it's not possible? Or just that it isn't preferrable?