For long lived Crop widgets (eg. widgets that are stored on navigator stack for some time and then pop-out to the user again) there was an issue that the Crop widget rendered blank background rather than actual image with cropping UI.
The issue was caused by premature call to _boundaries getter which depends on _surfaceKey.currentContext. The logic in didChangeDependencies was flawed because it was expecting _surfaceKey.currentContext to be present but didn't make sure that the build function already ran which would correctly assign GestureDetector's state and context to the key.
It wasn't an issue in earlier Flutter versions, but it is now and it have app-breaking potential.
For long lived
Cropwidgets (eg. widgets that are stored on navigator stack for some time and then pop-out to the user again) there was an issue that theCropwidget rendered blank background rather than actual image with cropping UI.The issue was caused by premature call to
_boundariesgetter which depends on_surfaceKey.currentContext. The logic indidChangeDependencieswas flawed because it was expecting_surfaceKey.currentContextto be present but didn't make sure that thebuildfunction already ran which would correctly assignGestureDetector'sstate and context to the key.It wasn't an issue in earlier Flutter versions, but it is now and it have app-breaking potential.