ActivityNavigator does not use NavTypes to encode arguments [383616432]

Fixed

Bug

Status Update

No update yet.

Description

il...@google.com

created issue #1

Dec 11, 2024 11:21PM

Component used: Navigation

Version used: 2.8.5

When ActivityNavigator fills in the intent.data, it seems to directly call Uri.encode(args[argName].toString()), thus bypassing any of the NavType specific logic for serializing the value into a String.

Comments

jb...@google.com <jb...@google.com> Dec 13, 2024 11:16PM

Reassigned to cl...@google.com.

cl...@google.com <cl...@google.com> Jan 7, 2025 12:06AM

Accepted by cl...@google.com.

ap...@google.com <ap...@google.com> #2Jan 7, 2025 01:09AM

Fixed with Change-Id: Iab75b018e47242e089ed317bc853a327849201bc

We still use DexSplitter when proguard is used for shrinking.

cl...@google.com <cl...@google.com> #3Jan 7, 2025 06:56PM

Marked as fixed.

Fixed internally and available in navigation 2.9.0-alpha05

na...@google.com <na...@google.com> #4Jan 29, 2025 06:12PM

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

androidx.navigation:navigation-runtime:2.9.0-alpha05
androidx.navigation:navigation-runtime:2.8.6

Issue 383616432