Switch controls with initial values error since friday update 4.1.16

Feedback

Hi,

Since the 4.1.16 update my app has started to fail due to a change in the way the model class is implemented for switch values

In the model the switch value was created this way:

bool? privateSwitchValue;

And now it has changed to this:

bool privateSwitchValue = true;

I have in these switches a InitialValue dynamic property that now it's not applied. I had to revert to a 4.1.15 generated version to be able to work.

I think this change breaks backward compatibility. It has happened to anyone? Why this change? Could you revert the change or at least create some sort of feature flag to not break backwards compatibility in a minor version?

6
4 replies