Navigation with null lists leads to indeterminate behavior [342672856]

Fixed

Bug

Status Update

No update yet.

Description

cl...@google.com

created issue #1

May 24, 2024 09:31PM

Null lists of built-in CollectionNavType such as StringListType, IntListType leads to different behavior depending on whether its string route or safe args, but either behavior seems wrong.

Take NavType.StringListType as example.

For string routes

val route = "test.com?list=null"
bundle[list] returns listOf("null")

For safe args

val route = MyRoute(null)
bundle is empty

Comments

ap...@google.com <ap...@google.com> #2May 28, 2024 02:33PM

Is there any way to use this while it's not available, without a big if else where we do everything duplicated? Like this example.

        val notification = if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.S) {
            Notification.Builder(...)
                .setContentTitle("Title")
                .setStyle(...)
                // Duplicate everything here!!!
                .build()
        } else {
            NotificationCompat.Builder(...)
                .setContentTitle("Title")
                .setStyle(...)
                // Duplicate everything here!!!
                .build()
        }

ap...@google.com <ap...@google.com> #3May 28, 2024 02:33PM

Hi,

Could you at least tell us if you will add the CallStyle to the NotificationCompat API?

Best regards,

ap...@google.com <ap...@google.com> #4May 31, 2024 05:50PM

Yes. Our goal is to provide an implementation that uses CallStyle on API 31+ and uses the new fields to produce a usable call notification, based on the device's standard template, on older versions of Android.

cl...@google.com <cl...@google.com> #5Jun 4, 2024 12:19AM

Marked as fixed.

Thanks for the answer. Do you have an estimated ETA?

ap...@google.com <ap...@google.com> #6Jun 6, 2024 06:19PM

Any update on this please?

pr...@google.com <pr...@google.com> #7Jun 12, 2024 10:45PM

Could you please give us an ETA?

Issue 342672856