Status Update
Comments
il...@google.com <il...@google.com>
il...@google.com <il...@google.com>
ap...@google.com <ap...@google.com> #2
It turns out this issue is due to by navArgs()
moving to navigation-common
, but the ProGuard rules still being located in the (now empty) navigation-common-ktx
. This means you can work around this issue by explicitly adding a dependency on androidx.navigation:navigation-common-ktx:2.4.0-alpha02
.
ap...@google.com <ap...@google.com> #3
Branch: androidx-main
commit 55af5f168e5a1e6dc73c8d35ac79598cb4ae5bd8
Author: Ian Lake <ilake@google.com>
Date: Wed Jun 09 16:57:14 2021
Move ProGuard rules from navigation-common-ktx to common
NavArgsLazy was moved to navigation-common, but
the related proguard-rules.pro wasn't moved with it.
This meant that apps that didn't specifically include
the (now empty) navigation-common-ktx artifact wouldn't
get the correct set of ProGuard rules.
Test: tested in sample app
BUG: 190082521
Relnote: "ProGuard rules for `by navArgs()` now properly
apply when using `navigation-common` or any artifacts
that depend on it."
Change-Id: I688009632403c98afe728d856ce91cd056ef32a5
M navigation/navigation-common-ktx/build.gradle
M navigation/navigation-common/build.gradle
M navigation/navigation-common/proguard-rules.pro
ap...@google.com <ap...@google.com> #4
This has been fixed internally and will be available in Navigation 2.4.0-alpha03.
jb...@google.com <jb...@google.com> #5
This has been added internally and will be available in the Navigation 2.3.0-alpha06 release.
m....@gmail.com <m....@gmail.com> #6
il...@google.com <il...@google.com> #7
Note that this bug only covers the work on the Navigation library side. We are working with the Android Studio team to add support to the Navigation Editor and to
Until those are completed, you won't see the mime type in the visual editor and generated <intent-filter>
elements won't include your mime type in its <data>
element. You'll want to define the app:mimeType
for your <deeplink>
in XML and add an <intent-filter>
manually to your manifest, respectively.
Description
Is it possible to use deep link in navigation component witn intent filer like content// or file//? For example: content://pl.solidexplorer2.files/storage/emulated/0/Download/test.txt. I think it will be helpful for apps with navigation component that should work with content provided by other apps (like file manager). I tried this: 1) Created intent filter for activity by myself:<intent-filter
android:icon="@mipmap/ic_launcher"
android:label="@string/app_name">
<action android:name="android.intent.action.VIEW" />
<action android:name="android.intent.action.EDIT" />
<category android:name="android.intent.category.DEFAULT" />
<data
android:host="*"
android:mimeType="*/*"
android:pathPattern=".*\\.txt"
android:scheme="content" />
</intent-filter>
2) Added deep link to my navigation graph:
<deepLink
android:id="@+id/deepLink"
app:uri="{path}.txt" />
But it seems not work. Intent delivered succesfully to activtiy and I can use it but navigaion component ignore it (I used logcat to print uri from intent)