Thanks for your responses. I researched a little bit more and I think it is a flutter bug introduced by 3.27.3 and its already fixed in the master brach on version 3.29.X as i tested.