Welcome to OStack Knowledge Sharing Community for programmer and developer-Open, Learning and Share
Welcome To Ask or Share your Answers For Others

Categories

0 votes
292 views
in Technique[技术] by (71.8m points)

android - navigation component popUpTo bug

Recently I ran into issue that I asked about here

But when trying to figure out what's happening I always stumble on the same problem.

Here's what I have - I have a collection, preview, edit fragments than I need to navigate between.

But after navigating from edit fragment to preview fragment I want the back button to take user to collection fragment instead of edit fragment, and it does that, but when trying to navigate further it crashes because the destination is said to be (view_fragment). Why is that, is it some sort of bug?

enter image description here

<fragment android:id="@+id/collection_fragment">
    <action
        android:id="@+id/action_collection_fragment_to_view_fragment"
        app:destination="@+id/view_fragment" />
</fragment>

<fragment android:id="@+id/view_fragment">
    <action
        android:id="@+id/action_view_fragment_to_edit_fragment"
        app:destination="@id/edit_fragment" />
    <argument android:name="item" />
</fragment>

<fragment android:id="@+id/edit_fragment">
    <action
        android:id="@+id/action_edit_fragment_to_view_fragment"
        app:destination="@id/view_fragment"
        app:popUpTo="@id/collection_fragment" />
    <argument android:name="item" />
</fragment>

EDIT:

Stack trace:

java.lang.IllegalArgumentException: navigation destination com.domain.application:id/action_collection_fragment_to_view_fragment is unknown to this NavController
    at androidx.navigation.NavController.navigate(NavController.java:669)
    at androidx.navigation.NavController.navigate(NavController.java:628)
    at com.domain.application.CollectionFragment$onActivityCreated$4.onChanged(CollectionFragment.kt:126)
    at com.domain.application.CollectionFragment$onActivityCreated$4.onChanged(CollectionFragment.kt:28)
    at com.domain.application.common.SingleLiveEvent$observe$1.onChanged(SingleLiveEvent.kt:20)
    at android.arch.lifecycle.LiveData.considerNotify(LiveData.java:109)
    at android.arch.lifecycle.LiveData.dispatchingValue(LiveData.java:126)
    at android.arch.lifecycle.LiveData.setValue(LiveData.java:282)
    at android.arch.lifecycle.MutableLiveData.setValue(MutableLiveData.java:33)
    at com.domain.application.common.SingleLiveEvent.setValue(SingleLiveEvent.kt:27)
    at android.arch.lifecycle.LiveData$1.run(LiveData.java:87)
    at android.os.Handler.handleCallback(Handler.java:789)
    at android.os.Handler.dispatchMessage(Handler.java:98)
    at android.os.Looper.loop(Looper.java:164)
    at android.app.ActivityThread.main(ActivityThread.java:6938)
    at java.lang.reflect.Method.invoke(Native Method)
    at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:327)
    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1374)
See Question&Answers more detail:os

与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…
Welcome To Ask or Share your Answers For Others

1 Answer

0 votes
by (71.8m points)

This was a bug in alpha04 version it's fixed in alpha05 https://issuetracker.google.com/issues/111907708


与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…
Welcome to OStack Knowledge Sharing Community for programmer and developer-Open, Learning and Share
Click Here to Ask a Question

...