Reference type aren't supported as deeplink arguments [179166693]

Fixed

Bug

androidx-bug-bounty

Status Update

No update yet.

Description

pa...@nearside.com

created issue #1

Feb 2, 2021 09:59PM

Component used: Navigation Version used: 2.3.3 (latest) Devices/Android versions reproduced on: n/a

setup:

destination (in Module B) has navigation arg of type reference
origin (in Module A) uses a deeplink with the query param ?description=R.string.foo
origin must toString R.string.foo in order to create a URI

Result:

java.lang.UnsupportedOperationException: References don't support parsing string values.

The workaround is obviously to change the nav arg type to String and call getString, but it's a weird limitation for sibling-module navigation.

Comments

il...@google.com <il...@google.com> #2Feb 2, 2021 10:04PM

Assigned to il...@google.com.

Nested scrolling works partially (as per

http://b/122818889). Let's discuss if we need full support and if so make sure it works.

pa...@nearside.com <pa...@nearside.com> #3Feb 2, 2021 10:06PM

Hi!

What is 'partially' exactly?
How do I see it?
Thanks!

il...@google.com <il...@google.com> #4Feb 2, 2021 10:10PM

As of now:
- Nesting scroll views with a scroll direction perpendicular to the ViewPager2's orientation inside ViewPager2 works
- Nesting scroll views with a scroll direction parallel to the ViewPager2's orientation inside ViewPager2 does not work

ap...@google.com <ap...@google.com> #5Feb 10, 2021 01:55AM

Marked as fixed.

Horizontal ViewPager2 not correctly working into a vertical RecyclerView
Set a setNestedScrollingEnabled to the RecyclerView into the ViewPager2 (across reflection) resolves the problem

Issue 179166693

Description

Issue summary

Comments

il...@google.com <il...@google.com> #2Feb 2, 2021 10:04PM

pa...@nearside.com <pa...@nearside.com> #3Feb 2, 2021 10:06PM

il...@google.com <il...@google.com> #4Feb 2, 2021 10:10PM

ap...@google.com <ap...@google.com> #5Feb 10, 2021 01:55AM

Add comment

Issue metadata