Parcelables don't support default values. Android navigation deeplink argument [148523779]

Infeasible

Bug

Status Update

No update yet.

Description

ni...@gmail.com

created issue #1

Jan 29, 2020 10:06PM

Components used: Navigation, Deeplink, SafeArgs, Parcelable
Version used: 2.2.0
Devices/Android versions reproduced on: Emulator all API's

During the implementation of the passing parameter solution, in navigation between modules, I came across a serialization error. Deeplinks, as far as I know, accepts custom argument types, which are Parcelables or Serializable.

Error message:

java.lang.UnsupportedOperationException: Parcelables don't support default values.

Am I doing something wrong or this is still under development?

Here is short example:

<fragment
android:id="@+id/sampleFragment"
android:name="com.testapp.app.samples.navigation.SampleFragment"
android:label="SampleFragment">
<argument
android:name="Args"
app:argType="com.testapp.navigation.SampleArgs" />
<deepLink app:uri="app://app/samples/navigation/SampleFragment?Args={Args}"/>
</fragment>

@Parcelize
@Keep data class SampleArgs(
val text: String
) : NavArgs, Parcelable

val x = SampleArgs("TEST")
val uri = Uri.parse("app://app/samples/navigation/SampleFragment?Args=$x}")
navController.navigate(uri)

Comments

il...@google.com <il...@google.com> #2Jan 29, 2020 10:16PM

It doesn't look like this bug has a link to the affected dataset(s) in Earth Engine. Please reply to this bug with a comment containing a URL of the form "https://developers.google.com/earth-engine/datasets/catalog/(ID)" or "https://developers.google.com/earth-engine/datasets/tags/(TAG)", filling in the (ID) or (TAG) with the appropriate value.

If this issue doesn't affect an existing dataset, consider moving in into the "Public Trackers > Earth Engine > Datasets > New Datasets" component. If the dataset is a new or updated version of an existing dataset, you can add the URL of the existing one. And if you cannot add a URL, you can disable future automated messages by adding a comment with "dataset_bug_ranker: disable" on its own line.

Reason: Issue does not contain a dataset URL. dataset_bug_ranker: remind=P7D

ni...@gmail.com <ni...@gmail.com> #3Jan 29, 2020 10:29PM

This is not for a dataset but google earth panels themselves

On Thu, 16 Jan 2025, 13:25 , <buganizer-system@google.com> wrote:

- Show quoted text -

ni...@gmail.com <ni...@gmail.com> #4Jan 29, 2020 10:40PM

If this is not the correct place to ask this question could you please
direct me to the appropriate place, many thanks

On Thu, Jan 16, 2025 at 1:39 PM Hope Irvine <hopekathleenirvine@gmail.com>
wrote:

- Show quoted text -

jo...@imdb.com <jo...@imdb.com> #5Dec 2, 2020 10:40PM

You probably just dragged the vertical divider too far to the right. Try dragging it back.

il...@google.com <il...@google.com> #6Dec 2, 2020 10:44PM

Closing as intended behavior. Use the panel handle to reduce the Code and Map panel area and increase the Console panel.

jo...@imdb.com <jo...@imdb.com> #7Dec 3, 2020 04:21PM

I see what you mean. I was thinking that methods like Bundle.putSerializable() / Bundle.getSerializable() were doing something like I describe and that the Nav component parsing would work similarly, but now I see that those just marshal the object reference, not to and from byte[] or String.

Does that mean there is no support for custom types being parsed from deep link placeholders even if I can implement the parse function? That is, will I need to parse from String to my custom type at each site at which I want to access this argument?

Thanks, Joel

ia...@gmail.com <ia...@gmail.com> #8Jul 22, 2021 01:13PM

This is a valid use case as we had just started a new project and were planning to use deep links to navigate between different feature modules. It looks like we won't be able to pass around parcelables or serializables using deep links. Is manual serialization only way to get around this?

pr...@gmail.com <pr...@gmail.com> #9Aug 11, 2021 11:23AM

noticed in compose navigation this is still happening

jb...@google.com <jb...@google.com> #10Feb 25, 2022 10:46PM

Status: Won't Fix (Infeasible)

There isn't much to be done to support this from the XML side but with https://issuetracker.google.com/196871885 you can do this type of thing if you use the Kotlin DSL. (Although you still need to use a serialization method.)

he...@gmail.com <he...@gmail.com> #11Jul 13, 2022 09:41AM

I'm amazed that this is dismissed as "Won't Fix (Infeasible)".
This basically scuppers any dream of migrating completely to composables with no fragments/xml because the new composable navigation arrangement can only support passing primitives.
With all of Google's resources, you'd think that we could have some sort of built-in solution that everyone could trust that doesn't involve reams of custom boilerplate.

jb...@google.com <jb...@google.com> #12Jul 14, 2022 12:25AM

From #6:

Serializable and Parcelable have no consistent API surface that would allow automatic parsing of a string into your custom class instance.

If you have a custom type, then yes you need to define how Navigation needs to handle that type.