Followup to #1315 The workaround introduced in 3b54903fea4493b38bab714d4fbf47a5ecb542ee can be removed once there's a new version of flutter_zxing with a fix, see linked PR in the original bug report
Followup to #1315
The workaround introduced in 3b54903 can be removed once there's a new version of flutter_zxing with a fix, see linked PR in the original bug report