androidx.navigation.dynamicfeatures.fragment.ui.AbstractProgressFragment navigate multiple time [169636207]

Fixed

Bug

Status Update

No update yet.

Description

pq...@gmail.com

created issue #1

Sep 30, 2020 04:14AM

Component used: androidx.navigation:navigation-dynamic-features-fragment

Version used:2.3.0 Devices/Android versions reproduced on: all devices/android versions

override fun onResume() { super.onResume() if (navigated) { findNavController().popBackStack() return } var monitor = installViewModel.installMonitor if (monitor == null) { Log.i(TAG, "onResume: monitor is null, navigating") navigate() monitor = installViewModel.installMonitor } if (monitor != null) { Log.i(TAG, "onResume: monitor is now not null, observing") monitor.status.observe(this, StateObserver(monitor)) } }

Any time onResume() is called, monitor.status observed. When dynamic feature module is installed, each StateObserver will call navigate() and destination activity/fragment will be navigated multiple time

Comments

jb...@google.com <jb...@google.com> Oct 2, 2020 07:20PM

Assigned to be...@google.com.

be...@google.com <be...@google.com> #2Oct 5, 2020 03:18PM

Project: platform/frameworks/support
Branch: androidx-main

commit 81120ca77c09c437775232585652b293ed572d45
Author: Clara Fok <clarafok@google.com>
Date: Thu Feb 29 17:29:44 2024

Paging to use common MainThread annotation

Test: ANDROIDX_PROJECTS=INFRAROGUE ./gradlew paging:paging-common:allTest
Bug: 327682438
Change-Id: I78f0d3cf36e3a3a9088e0698c351289cf2dbc1bf

M paging/paging-common/build.gradle
D paging/paging-common/src/commonJvmAndroidMain/kotlin/androidx/paging/MainThread.jvm.kt
D paging/paging-common/src/commonMain/kotlin/androidx/paging/MainThread.kt
M paging/paging-common/src/commonMain/kotlin/androidx/paging/PagingDataPresenter.kt

https://android-review.googlesource.com/2984997

ap...@google.com <ap...@google.com> #3Nov 4, 2020 06:40PM

Fixed internally and available in paging-3.3.0-alpha05

il...@google.com <il...@google.com> #4Nov 4, 2020 07:14PM

Marked as fixed.

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

androidx.paging:paging-common:3.3.0-alpha05
androidx.paging:paging-common-android:3.3.0-alpha05
androidx.paging:paging-common-iosarm64:3.3.0-alpha05
androidx.paging:paging-common-iossimulatorarm64:3.3.0-alpha05
androidx.paging:paging-common-iosx64:3.3.0-alpha05
androidx.paging:paging-common-jvm:3.3.0-alpha05
androidx.paging:paging-common-linuxx64:3.3.0-alpha05
androidx.paging:paging-common-macosarm64:3.3.0-alpha05
androidx.paging:paging-common-macosx64:3.3.0-alpha05

b9...@gmail.com <b9...@gmail.com> #5Dec 14, 2020 05:37PM

#4 I think this fix break the behavior of DefaultProgressFragment, it doesn't call super.onViewCreated() so that the installation won't execute.

be...@google.com <be...@google.com> #6Dec 14, 2020 05:58PM

onViewCreated on Fragment is a GNDN function, so no need to override it.

Can you provide more information as to how your installation won't execute?

b9...@gmail.com <b9...@gmail.com> #7Dec 14, 2020 07:28PM

Move install monitor observation to onViewCreated

DefaultProgressFragment won't execute super(AbstractProgressFragment)'s onViewCreated(). So after this change, DefaultProgressFragment can't monitor the installation progress.

b9...@gmail.com <b9...@gmail.com> #8Dec 14, 2020 07:33PM

TL;DR

Call super.onViewCreated(view, savedInstanceState) in DefaultProgressFragment will solve this issue.

ap...@google.com <ap...@google.com> #9Dec 15, 2020 05:32PM

Project: platform/frameworks/support
Branch: androidx-master-dev

commit 524a4f074b688975041f6ddd9db9eb31a88410e8
Author: Ben Weiss <benweiss@google.com>
Date: Tue Dec 15 12:26:06 2020

Add missing onViewCreated call

DefaultProgressFragment did not call super.onViewCreated which
could lead to installation progress not completing.

Bug: 169636207
Test: N/A
RelNote: Fix stuck installation progress
Change-Id: Ib27a77bc4572fc69cea38d738255c987449d6137

M navigation/navigation-dynamic-features-fragment/src/main/java/androidx/navigation/dynamicfeatures/fragment/ui/DefaultProgressFragment.kt

https://android-review.googlesource.com/1529306

b9...@gmail.com <b9...@gmail.com> #10Feb 4, 2021 04:07PM

Why this fix doesn't included in 2.3.3?

il...@google.com <il...@google.com> #11Feb 10, 2021 01:03AM

Re #10, yes, you're right this didn't make it into Navigation 2.3.3. Sorry about that. We'll look at doing a Navigation 2.3.4 with this fix.

b9...@gmail.com <b9...@gmail.com> #12Mar 6, 2021 03:47PM

#11 Still no 2.3.4 released.

za...@gmail.com <za...@gmail.com> #13Jul 4, 2022 02:51PM

I believe I'm facing another issue because of this fix:

When navigating to an activity that belongs to a dynamic module, the AbstractProgressFragment is not removed from the back stack. The line that's supposed to do it was moved from onResume to onViewCreated:

if (navigated) {
    findNavController().popBackStack()
    return
}

And onViewCreated is not called since we're coming back from another activity.

Moving that block back to the onResume method should solve the problem. In the meantime (as a workaround), I guess we can do as follows:

class CustomProgressFragment : AbstractProgressFragment() {

    private var navigated = false

    override fun onResume() {
        super.onResume()
        // Workaround:
        // AbstractProgressFragment is not being removed from the back stack when returning from another activity
        if (navigated) findNavController().popBackStack()
    }

    override fun onInstalled() {
        testing = true
    }
   
   ...
   ...
}

za...@gmail.com <za...@gmail.com> #14Jul 4, 2022 02:54PM

Update: Regarding the workaround I mentioned, this is the correct implementation of the onInstalled method

    override fun onInstalled() {
        navigated = true
    }

il...@google.com <il...@google.com> #15Jul 13, 2022 11:18PM

Re comment#13 - please file a separate bug with a sample project that reproduces your issue. onViewCreated() is indeed called when you return to the AbstractProgressFragment from another fragment, which is the only thing your newly loaded graph should have as its start destination. You...don't happen to have a start destination that is an activity destination? You shouldn't be using Dynamic Navigation at all in that case (as the system will auto-download the module your activity is in upon request).