IssueTracker

Hello.

This crash still occurs.

• CAMERAX VERSION: 1.0.0-beta4
• ANDROID OS BUILD NUMBER: Android 7.1.1
• DEVICE NAME: FUJITSU F-02H

We receive following crash report from FUJITSU F-02H. So far We have received this crash report only from F-02H.

java.lang.IllegalArgumentException
Can not get supported output size under supported maximum for the format: 34

androidx.camera.camera2.internal.SupportedSurfaceCombination.getSupportedOutputSizes (SupportedSurfaceCombination.java:349)
androidx.camera.camera2.internal.SupportedSurfaceCombination.getSuggestedResolutions (SupportedSurfaceCombination.java:197)
androidx.camera.camera2.internal.Camera2DeviceSurfaceManager.getSuggestedResolutions (Camera2DeviceSurfaceManager.java:198)
androidx.camera.core.CameraX.calculateSuggestedResolutions (CameraX.java:949)
androidx.camera.core.CameraX.bindToLifecycle (CameraX.java:351)
androidx.camera.lifecycle.ProcessCameraProvider.bindToLifecycle (ProcessCameraProvider.java:230)
(our application's package name).CameraFragment.bindCameraUseCases (CameraFragment.java:174)

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

Yes

2. 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.

Hello.

2. 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)
        }
      }
    }

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.

I hope you can excuse me for the delayed response. We have put up a new solution that should contain the expected behavior. If the calling application uses a cancellable scope as @he...@google.com mentioned above, a proper JobCancellationException will be thrown. If a non cancellable scope is used, even on configuration change, our library will ensure proper return of credentials. You can expect this change to arrive in the next release, around May.

In the meantime, to try this out you can use a snapshot SDK from https://androidx.dev/. Any buildId >= 9928302 works. Here's an example of using the 9928302 snapshot:

Step 1: Add the following maven url line to your build.gradle file.

allprojects {
    repositories {
        google()
        jcenter()
        maven { url 'https://androidx.dev/snapshots/builds/9928302/artifacts/repository' }
    }
}

Step 2: Depend on the snapshot version artifact:

dependencies {
    def work_version = '1.0.0-SNAPSHOT'
    implementation "androidx.credentials:credentials-play-services-auth:$work_version"
    ...
}

Thank you for your patience, and please let us know if there are any other issues. We appreciate your help in making Credential Manager better prior to the final launch.

I confirm that issue is fixed. Thanks! However memory leak is still present. Will open another issue for that.

The following release(s) address this bug.It is possible this bug has only been partially addressed:

• androidx.credentials:credentials-play-services-auth:1.0.0-alpha07

This looks like a different issue, could you please open a new bug with more details about which version of jetpack you're using, which version of android you're running, a bug report and etc.