You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Wondering if anyone else has experienced this and how they may have gotten around it:
I'm encountering an intermittent issue where the Mobile Scanner widget's camera preview sometimes fails to display, showing only a blank or static background (e.g., a green bar on a white background), even though the underlying scanner remains active and successfully detects QR codes. This behavior is accompanied by warnings in the system logs that look like this:
W/System (XXXX): A resource failed to call release.
I/BpBinder(XXXX): onLastStrongRef automatically unlinking death recipients:
W/System (XXXX): A resource failed to call release.
I/BpBinder(XXXX): onLastStrongRef automatically unlinking death recipients:
The issue appears to be highly timing-dependent: the shorter the duration spent on other screens (e.g., the app's home screen is where i currently navigate from/to the scanner screen) before returning to the scanner screen, the more likely the camera preview is to be blank. Conversely, waiting for a longer period (e.g., 5-10 seconds) before returning makes the camera preview consistently appear correctly. For now, I have placed a 2 second delay (via a Future.delayed(const Duration(milliseconds: 2000))) before calling _scannerController.start() and it seems to consistency show the camera preview, further suggesting a timing-related issue.
Wondering if some sort of race condition or maybe the delayed resource release is an issue within the plugin's native camera management?
Additional Context:
The application explicitly disposes and re-creates a new MobileScannerController instance whenever the ScreenOneScanning state is entered (e.g., after a successful scan and reset, or on AppLifecycleState.resumed).
Project is Flutter 3.27.3, Dart 3.6.1, mobile Scanner 6.0.10
Device is Samsung S10e, Android 12.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Wondering if anyone else has experienced this and how they may have gotten around it:
I'm encountering an intermittent issue where the Mobile Scanner widget's camera preview sometimes fails to display, showing only a blank or static background (e.g., a green bar on a white background), even though the underlying scanner remains active and successfully detects QR codes. This behavior is accompanied by warnings in the system logs that look like this:
W/System (XXXX): A resource failed to call release.
I/BpBinder(XXXX): onLastStrongRef automatically unlinking death recipients:
W/System (XXXX): A resource failed to call release.
I/BpBinder(XXXX): onLastStrongRef automatically unlinking death recipients:
The issue appears to be highly timing-dependent: the shorter the duration spent on other screens (e.g., the app's home screen is where i currently navigate from/to the scanner screen) before returning to the scanner screen, the more likely the camera preview is to be blank. Conversely, waiting for a longer period (e.g., 5-10 seconds) before returning makes the camera preview consistently appear correctly. For now, I have placed a 2 second delay (via a Future.delayed(const Duration(milliseconds: 2000))) before calling _scannerController.start() and it seems to consistency show the camera preview, further suggesting a timing-related issue.
Wondering if some sort of race condition or maybe the delayed resource release is an issue within the plugin's native camera management?
Additional Context:
The application explicitly disposes and re-creates a new MobileScannerController instance whenever the ScreenOneScanning state is entered (e.g., after a successful scan and reset, or on AppLifecycleState.resumed).
Project is Flutter 3.27.3, Dart 3.6.1, mobile Scanner 6.0.10
Device is Samsung S10e, Android 12.
Beta Was this translation helpful? Give feedback.
All reactions