Crash : IllegalArgumentException Can not get supported output size under supported maximum for the format: 34 [150506192]

Fixed

Bug

Status Update

No update yet.

Description

vi...@gmail.com

created issue #1

Feb 29, 2020 03:18AM

CAMERAX VERSION (ex - 1.0.0-alpha07)

1.0.0-alpha07

DEVICE NAME: (Nexus 5X, Samsung S6, etc)

name : FUJITSU arrowsM04
Android OS version : 7.1.1

name: FUJITSU F-04J
Android OS version : 6.0.1

name: FUJITSU F-05J
Android OS version : 7.1.1

DESCRIPTION:

We receive following crash report from our app user.

Fatal Exception: java.lang.IllegalArgumentException: Can not get supported output size under supported maximum for the format: 34
at a.c.a.b.k0.a + 98(SupportedSurfaceCombination.java:98)
at a.c.a.b.k0.a + 30(SupportedSurfaceCombination.java:30)
at a.c.a.b.t.a + 22(Camera2DeviceSurfaceManager.java:22)
at androidx.camera.core.k1.a + 98(CameraX.java:98)
at androidx.camera.core.k1.a + 22(CameraX.java:22)
at a.c.b.c.a + 6(ProcessCameraProvider.java:6)
at <out app package name>.CameraFragment.a + 33(CameraFragment.kt:33)
at <out app package name>.CameraFragment.a + 1(CameraFragment.kt:1)
at <out app package name>.CameraFragment$m.run + 1(CameraFragment.kt:1)
at android.os.Handler.handleCallback + 751(Handler.java:751)
at android.os.Handler.dispatchMessage + 95(Handler.java:95)
at android.os.Looper.loop + 154(Looper.java:154)
at android.app.ActivityThread.main + 6262(ActivityThread.java:6262)
at java.lang.reflect.Method.invoke(Method.java)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run + 890(ZygoteInit.java:890)
at com.android.internal.os.ZygoteInit.main + 780(ZygoteInit.java:780)

REPRODUCIBILITY: (5 of out 5, 1 out of 100, etc)

We receive this crash report from only three devices. And these devices's manufacturer is FUJITSU.

ADDITIONAL INFORMATION:

CODE FRAGMENTS (this will help us troubleshoot your issues):

Our app bind usecases by following code.

private fun bindCameraUseCases(processCameraProvider: ProcessCameraProvider) {
preview = Preview.Builder().apply {
setTargetAspectRatio(AspectRatio.RATIO_4_3)
}.build().apply {
previewSurfaceProvider = binding.previewViewCamera.previewSurfaceProvider
}

imageCapture = ImageCapture.Builder().apply {
setCaptureMode(ImageCapture.CaptureMode.MINIMIZE_LATENCY)
setTargetAspectRatio(AspectRatio.RATIO_4_3)
setFlashMode(FlashMode.OFF)
}.build()

val cameraSelector = CameraSelector.Builder().requireLensFacing(LensFacing.BACK).build()
processCameraProvider.bindToLifecycle(viewLifecycleOwner, cameraSelector, preview, imageCapture)
}

Comments

er...@google.com <er...@google.com> #2Mar 2, 2020 11:39PM

Reassigned to vi...@gmail.com.

Yes, this is correct. Having individual navigation graphs on each activities overrides or disallow up navigation to the main activity.

er...@google.com <er...@google.com> #3Mar 4, 2020 06:16PM

Reassigned to ca...@google.com.

I believe I have found the potential problem that is causing this:
// @ androidx.navigation.NavController
// line 124

// Now record the pop operation that we were sent
if (!mBackStack.isEmpty()) {
mBackStack.removeLast();
}
// We never want to leave NavGraphs on the top of the stack
while (!mBackStack.isEmpty()
&& mBackStack.peekLast() instanceof NavGraph) {
popBackStack();
}

the condition in while loop is never satisfied because of the above `if` statement above it has already removed the last item of the mBackStack (which was the NavGraph) and thus popBackStack() is never called again.

ch...@google.com <ch...@google.com> Mar 5, 2020 02:41AM

Reassigned to ch...@google.com.

ch...@google.com <ch...@google.com> #4Mar 5, 2020 02:59AM

According to Ian Lake, NavigationUI does not support up navigation yet, that is why this is a feature request.

+Pedro Varela - we don't support navigating up through activities as part of NavigationUI yet, please star the feature request:

https://issuetracker.google.com/issues/79993862 (this issue)

ch...@google.com <ch...@google.com> Mar 9, 2020 11:09AM

Accepted by ch...@google.com.

vi...@gmail.com <vi...@gmail.com> #5Mar 11, 2020 07:15AM

Ian Lake said Up navigation is not supported through activities, only through fragments.

ch...@google.com <ch...@google.com> #6Mar 18, 2020 07:49AM

Marked as fixed.

With the introduction of AppBarConfiguration, this is now possible with the setupActionBarWithNavController method by using an empty set of top level destinations (to always show the up button) and then overriding onSupportNavigateUp() as per the documentation:

https://developer.android.com/topic/libraries/architecture/navigation/navigation-ui#action_bar

I'll leave this bug open as we still need an equivalent API for the Toolbar versions.

vi...@gmail.com <vi...@gmail.com> #7Jul 5, 2020 07:23AM

https://android-review.googlesource.com/846338 adds a setFallbackOnNavigateUpListener method on AppBarConfiguration that allows you to register an OnNavigateUpListener to handle cases where navController.navigateUp() return false.

This allows you to call onSupportNavigateUp() (or super.onSupportNavigateUp() if you're using an ActionBar) from that method to have your Up button transition between activities.

This will be available in 1.0.0-alpha09.

ch...@google.com <ch...@google.com> #8Jul 6, 2020 01:41AM

There is Jarks when implementing this way to navigate up between activities.

vi...@gmail.com <vi...@gmail.com> #9Jul 8, 2020 07:46AM

Is the full name of the device Fujitsu Arrows NX F-02H that has a 1440x2560 display?

Yes

Please help to provide the supported output sizes of ImageFormat.PRIVATE that is obtained by StreamConfigurationMap#getOutputSizes(int).

Since we don't have this device, we'll try to collect this information in the next version of our app. The next version will be released later this month.

vi...@gmail.com <vi...@gmail.com> #10Oct 13, 2020 02:44AM

Hello.

Please help to provide the supported output sizes of ImageFormat.PRIVATE that is obtained by StreamConfigurationMap#getOutputSizes(int).

We have collected the output of the device where the crash occurs.

Device1

Model : arrows Be F-05J
Android Version : 7.1.1
Supported output sizes of ImageFormat.PRIVATE

CameraId 0: 480x480
CameraId 1: 2048x1536 ,1920x1080 ,1280x720 ,960x720 ,640x480 ,320x240 ,176x144

Device2

Model : Fujitsu arrows M04
Android Version : 7.1.1
Supported output sizes of ImageFormat.PRIVATE

CameraId 0: 480x480
CameraId 1: 2048x1536 ,1920x1080 ,1280x720 ,960x720 ,640x480 ,320x240 ,176x144

Additional Information

CameraX version : 1.0.0-beta04

We collect the supported output sizes by following code.

val errorString = buildString {
      append("The supported output sizes of ImageFormat.PRIVATE: ")

      (requireContext().getSystemService(Context.CAMERA_SERVICE) as CameraManager).apply {

        cameraIdList.forEachIndexed { index, cameraId ->
          val msg = if (VERSION.SDK_INT >= VERSION_CODES.M) {
            val configurationMap =
              getCameraCharacteristics(cameraId).get(CameraCharacteristics.SCALER_STREAM_CONFIGURATION_MAP)
            val sizes = configurationMap?.getOutputSizes(ImageFormat.PRIVATE)
            "CameraId $index: ${sizes?.joinToString(" ,")}"
          } else {
            "CameraId $index: This device version is under M."
          }
          append(msg)
        }
      }
    }

vi...@gmail.com <vi...@gmail.com> #11Jan 3, 2021 10:57AM

Hello. Any updates?

ch...@google.com <ch...@google.com> #12Jan 5, 2021 02:40AM

I tried to find the device specs and both Fujitsu arrows Be F-05J and Fujitsu arrows M04 should have 720x1280 size display. For the camera id 0 device, it is a different case that the display size is larger than 640x480 but the device only supports a 480x480 size. The case also caused the same IllegalArgumentException and was also fixed by aosp/1254406 that was merged in 2020/05/17 and should be included in 1.0.0-beta04 release. Before aosp/1254406 was merged, the only 480x480 size would be filtered out and then caused the IllegalArgumentException. After it was merged, the 640x480 size threshold was removed and then the 480x480 size would be kept and selected to use.

It looks like 1.0.0-beta04 release had been used to collect the supported sizes information. But the issue should have been fixed by 1.0.0-beta04 release. Did you only check the device model name to collect the supported sizes information or collect the information when the IllegalArgumentException issue happens again?

CameraX's 1.0.0-rc01 version has been released. There should be many fixes included in it compared to the 1.0.0-beta04 version. Maybe you can also consider to upgrade to the latest 1.0.0-rc01 version for your application. Thanks.

vi...@gmail.com <vi...@gmail.com> #13Jan 8, 2021 07:48AM

Did you only check the device model name to collect the supported sizes information or collect the information when the IllegalArgumentException issue happens again?

We collect informations only from the device on which IllegalArgumentException happened.

Our latest app uses CameraX version 1.0.0-beta10 and this issue still occurres.

However we don't receive crash report from Fujitsu arrows Be F-05J or Fujitsu arrows M04 so far. (This doesn't mean this issue is fixed on these devices because our app is heavily rely on camera so these device's user wouldn't use our app anymore.)

Instead, we receive crash report from Fujitsu F-03K.

Model : Fujitsu F-03K
Android Version : 7.1.2
Supported output sizes of ImageFormat.PRIVATE

CameraId 0 : 480x480
CameraId 1 : 2048x1536 ,1920x1080 ,1280x720 ,960x720 ,640x480 ,320x240 ,176x144

ch...@google.com <ch...@google.com> #14Jan 8, 2021 10:09AM

Status: In Progress (Accepted) (reopened)

I missed some settings when I simulated the issue by robolectric test so that I was not able to reproduce it. Now, I can reproduce the issue if the device only supports one 480x480 resolution. I'm working on the solution and target to make it included in next release.

ap...@google.com <ap...@google.com> #15Jan 12, 2021 02:10AM

Project: platform/frameworks/support
Branch: androidx-main

commit 69d15dff7bb857ee33a0f643ff42a0f8bc475ab2
Author: charcoalchen <charcoalchen@google.com>
Date: Fri Jan 08 18:30:03 2021

Fixed IllegalArgumentException issue happened when all preview supported sizes are smaller than 640x480 and display size is larger than 640x480.

Do not filter out sizes smaller than 640x480 when all preview supported sizes are smaller than 640x480 and display size is larger than 640x480.

Relnote:"Fixed IllegalArgumentException issue happened when all preview supported sizes are smaller than 640x480 and display size is larger than 640x480."

Bug: 150506192
Test: SupportedSurfaceCombinationTest
Change-Id: I2a63ce8e2ad42a9cc060c8635ac3603bf440b1ec

M camera/camera-camera2/src/main/java/androidx/camera/camera2/internal/SupportedSurfaceCombination.java
M camera/camera-camera2/src/test/java/androidx/camera/camera2/internal/SupportedSurfaceCombinationTest.java

https://android-review.googlesource.com/1545624

ch...@google.com <ch...@google.com> #16Jan 12, 2021 02:49AM