Thanks for writing to us. We will look into the issue. Meanwhile can you use the previous version to avoid any production degradations.

@DK070202 I think better to implement deprecated warning first before breaking changes.

We have version 1.1.1 in our project. After updating to 1.2.0 we got an error

@DK070202 I think it is better to implement a deprecated warning first before breaking changes.

Thanks, for choosing the Growthbook and for this feedback.

Yes, I do agree when changes are going to be breaking changes, will incorporate such warnings in the future version before such major changes. With that, we are going to roll out a new major version of SDK 2.0.0 that partially solves this. As package publishing process on the pub is an irreversible process.