Can't open the compose destination using deeplink after library bump [399826566]

Fixed

Bug

Status Update

No update yet.

Description

sy...@airthings.com

created issue #1

Feb 28, 2025 02:00PM

Component used: Navigation (androidx.navigation:navigation-compose)
Version used: 2.8.8
Devices/Android versions reproduced on:
Pixel 8 Pro

Issue description:
I have an app with Compose and 2 simple destinations: start destination "home" and deeplink destination "url"
I was able to access the "url" screen by launching:
adb shell am start -W -a android.intent.action.VIEW -d "xiver://

www.xiver.com/dsfds/32"
Last 2 fields: "dsfds" and "32" are parameters.

After library update from 2.7.7 to 2.8.8 it stopped working and now only "home" destination is opened.

If this is a bug in the library, we would appreciate if you could attach:
- Sample project to trigger the issue. [ATTACHED]

DeepLinking.zip

42 MB

Download

Comments

jb...@google.com <jb...@google.com> Feb 28, 2025 04:19PM

Assigned to cl...@google.com.

cl...@google.com <cl...@google.com> #2Feb 28, 2025 06:08PM

Status: Assigned (reopened)

Hi,

Thank you for your feedback. Could you help provide logs when the issue occurs and if possible a code snippet of the part that uses CameraX, it will help us find the root cause.

A quick question: does this issue occur on other devices, or only on Samsung Galaxy M55.

Message last modified on Feb 28, 2025 06:15PM

cl...@google.com <cl...@google.com> #3Feb 28, 2025 06:57PM

Hey,
attaching the logs.
The issue is only reproducible of M55. We have not met this on any other.

ap...@google.com <ap...@google.com> #4Mar 1, 2025 01:35AM

Thank you,

CameraX uses OpenGL for sharing stream between Preview and VideoCapture to provide use case combinations beyond device's native capabilities. When using Preview + ImageAnalysis or Preview + VideoCapture, the device capabilities are usually not exceeded, so stream sharing is not used. So this could be a device specified issue related to OpenGL.

We will attempt to acquire the reported device model for testing.

jb...@google.com <jb...@google.com> #5Mar 3, 2025 04:08PM

Thanks for the update,
Yes I'm aware that stream sharing is not a hardware supported feature.
Please let me know if we could assist in any way to solve the issue.

jb...@google.com <jb...@google.com> Mar 3, 2025 05:14PM

Marked as fixed.

na...@google.com <na...@google.com> #6Mar 12, 2025 06:12PM

Hey guys,
Is there any update on this? Were you able to find the phone? Could we assist here somehow?

jb...@gmail.com <jb...@gmail.com> #7Mar 14, 2025 04:02PM

Thank you for your kind reply! I think we will receive the phone in a while and we will update if we find anything.

Message last modified on Mar 14, 2025 04:10PM

cl...@google.com <cl...@google.com> #8Mar 14, 2025 04:06PM

Hi,

We got the device and did some investigating. The root cause seems to be that Samsung M55 has issues when using ImageAnalysis with another stream that uses TEMPLATE_RECORD, which is typically used by VideoCapture or by a stream shared between VideoCapture and Preview.

The issue also occurs when only ImageAnalysis and VideoCapture are bound. The video can only obtain the first few frames in this case.

We will fix this issues in a future release. One workaround you can try is to bind an additional ImageCaputre usecase (binds all 4 usecases), it seems the stream is normal in this situation.

Thanks for finding this bug!