Fixed
Status Update
Comments
ap...@google.com <ap...@google.com> #2
Thanks for reporting. We will look into the issue and update the status here.
ap...@google.com <ap...@google.com> #3
Hi Thanks for reporting the issue. To have more context, can you help provide the following information ?
-
Can you show us how you configure the ImageCapture in the codes ?
-
Did you enable CameraX Extensions ?
-
so the occurrence rate is like 20%, right ?
ap...@google.com <ap...@google.com> #4
Thanks for your response.
Sure. I can provide more data.
1.
ImageCapture.Builder builder = new ImageCapture.Builder();
builder.setCaptureMode(ImageCapture.CAPTURE_MODE_MINIMIZE_LATENCY);
if (!extensionAvailable) {
builder.setBufferFormat(ImageFormat.YUV_420_888);
}
imageCapture = builder.build();
UseCaseGroup useCaseGroup = new UseCaseGroup.Builder()
.addUseCase(preview)
.addUseCase(imageCapture)
.setViewPort(viewPort)
.build();
cameraProvider.unbindAll();
camera = cameraProvider.bindToLifecycle(this, cameraSelector, useCaseGroup);
-
Yes, Extensions are enabled, which means that the code is not configuring the buffer format and therefore will use the JPEG format. If I disable the extensions, than the error disapears. But I think its more a jpeg format issue then an extension problem.
-
Yes, occurrence rate is 20%.
ch...@google.com <ch...@google.com> #5
Thanks for the information! We will look into this.
na...@google.com <na...@google.com> #6
Any updates on this?
al...@gmail.com <al...@gmail.com> #7
Yes, we are able to reproduce it and are developing a fix to this.
Description
We should change Shapes to remove the Android-isms. potentially by using the existing abstractions that Compose already has for these types (same names, except PointF -> Offset)