This may be more a question than a bug-report, but here goes:
The NativeScript MLKit plugin v2.0.0 is using
'io.github.triniwiz:fancycamera:3.0.6'
and after releasing a new version of our app with that plugin (for barcode scanning), we are getting crash reports in Crashlytics containing:
Caused by java.lang.IllegalArgumentException
No supported surface combination is found for camera device - Id : 0. May be attempting to bind too many use cases.
Existing surfaces: [AttachedSurfaceInfo{surfaceConfig=SurfaceConfig{configType=PRIV, configSize=PREVIEW}, imageFormat=34, size=1440x1080, targetFrameRate=null},
AttachedSurfaceInfo{surfaceConfig=SurfaceConfig{configType=YUV, configSize=VGA}, imageFormat=35, size=640x480, targetFrameRate=null}] New configs: [androidx.camera.core.impl.ImageAnalysisConfig@3cea91e,
androidx.camera.core.impl.PreviewConfig@cece959]
with trace
Caused by java.lang.IllegalArgumentException
No supported surface combination is found for camera device - Id : 0. May be attempting to bind too many use cases.
Existing surfaces: [AttachedSurfaceInfo{surfaceConfig=SurfaceConfig{configType=PRIV, configSize=PREVIEW}, imageFormat=34, size=1440x1080, targetFrameRate=null},
AttachedSurfaceInfo{surfaceConfig=SurfaceConfig{configType=YUV, configSize=VGA}, imageFormat=35, size=640x480, targetFrameRate=null}] New configs: [androidx.camera.core.impl.ImageAnalysisConfig@3cea91e, androidx.camera.core.impl.PreviewConfig@cece959]
androidx.camera.lifecycle.LifecycleCameraRepository.bindToLifecycleCamera (LifecycleCameraRepository.java:285)
androidx.camera.lifecycle.ProcessCameraProvider.bindToLifecycle (ProcessCameraProvider.java:363)
io.github.triniwiz.fancycamera.Camera2.initPreview (Camera2.kt:909)
io.github.triniwiz.fancycamera.Camera2.refreshCamera (Camera2.kt:984)
io.github.triniwiz.fancycamera.Camera2.startPreview (Camera2.kt:1035)
io.github.triniwiz.fancycamera.FancyCamera.startPreview (FancyCamera.kt:365)
com.tns.Runtime.callJSMethodNative (Runtime.java)
com.tns.Runtime.dispatchCallJSMethodNative (Runtime.java:1301)
com.tns.Runtime.callJSMethodImpl (Runtime.java:1187)
com.tns.Runtime.callJSMethod (Runtime.java:1174)
com.tns.Runtime.callJSMethod (Runtime.java:1152)
com.tns.Runtime.callJSMethod (Runtime.java:1148)
com.tns.FragmentClass.onCreateView (FragmentClass.java:55)
androidx.fragment.app.Fragment.performCreateView (Fragment.java:3104)
com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1067)
Unfortunately, I cannot reproduce this in a simple test case.
Is there anything you know of that can avoid this?
This may be more a question than a bug-report, but here goes:
The NativeScript MLKit plugin v2.0.0 is using
'io.github.triniwiz:fancycamera:3.0.6'
and after releasing a new version of our app with that plugin (for barcode scanning), we are getting crash reports in Crashlytics containing:
with trace
Unfortunately, I cannot reproduce this in a simple test case.
Is there anything you know of that can avoid this?