Fixed

Bug

Status Update

No update yet.

Description

[Deleted User]

created issue #1

Apr 21, 2023 06:57PM

Versions

Component used: Navigation

Version used: 2.5.3

Devices/Android versions reproduced on: any

Description

According to the documentation of [BackHandler], nested BackHandlers(https://developer.android.com/reference/kotlin/androidx/activity/compose/package-summary#top-level-functions) should take priority:

If this is called by nested composables, if enabled, the inner most composable will consume the call to system back and invoke its lambda. The call will continue to propagate up until it finds an enabled BackHandler.

However, this doesn't work correctly if the activity is paused and then resumed.

Steps to reproduce

Start the app
Click back button
Toast "Button clicked" shows
Minimize the app (by pressing home button)
Bring app to foreground (via recent apps menu)
Click back button Expected behavior: Toast "Button clicked" shows Actual behavior: Toast "This should never ever show!!!" shows

Code to demonstrate the issue

class MainActivity : ComponentActivity() {
    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)
        setContent {
            MaterialTheme {
                Surface(Modifier.fillMaxSize()) {
                    val context = LocalContext.current
                    BackHandler {
                        Toast.makeText(context, "This should never ever show!!!", Toast.LENGTH_SHORT).show()
                    }
                    SampleApp()
                }
            }
        }
    }
}

@Composable
fun SampleApp() {
    val navController = rememberNavController()
    NavHost(navController, "first") {
        composable("first") { Screen() }
    }
}

@Composable
fun Screen() {
    val context = LocalContext.current
    BackHandler {
        Toast.makeText(context, "Back clicked", Toast.LENGTH_SHORT).show()
    }
    Column {
        Text("First screen")
    }
}

A sample project is attached.

MyApplication.zip

29 MB

Download

Comments

jb...@google.com <jb...@google.com> #2Apr 25, 2023 11:08PM

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

[Deleted User] <[Deleted User]> #3Apr 25, 2023 11:16PM

Fixed internally and available in paging-3.3.0-alpha05

il...@google.com <il...@google.com> Apr 26, 2023 11:44PM

Assigned to jb...@google.com.

jb...@google.com <jb...@google.com> #4Apr 27, 2023 12:26AM

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

ap...@google.com <ap...@google.com> #5Jun 1, 2023 12:50AM

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

commit d2c5efe67531a30fb9f1a129d52beb1e9ece0b29
Author: Jeremy Woods <jbwoods@google.com>
Date: Wed May 31 23:09:54 2023

Integrate BackHandler into NavHost

Instead of NavHost taking over the onBackPressedDispatcher from the
Activity, we should just make it use a BackHandler. This will ensure
that it interacters with the other BackHandlers in Compose correctly.

RelNote: "`NavHost` now correctly intercepts system back calls even
after the Activity has been `STOPPED` and `RESUMED`."
Test: modified tests
Bug: 279118447

Change-Id: Icb6deab996d122487243f0d3d775af8c15fc7c25

M navigation/navigation-compose/src/androidTest/java/androidx/navigation/compose/NavHostTest.kt
M navigation/navigation-compose/src/main/java/androidx/navigation/compose/NavHost.kt

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

il...@google.com <il...@google.com> #6Jun 1, 2023 05:00PM

Marked as fixed.

This has been fixed internally and will be available in Navigation 2.7.0-beta01.

pr...@google.com <pr...@google.com> #7Jun 8, 2023 01:31AM

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

androidx.navigation:navigation-compose:2.7.0-beta01

an...@daresay.co <an...@daresay.co> #8Jun 26, 2023 12:35PM

Comment has been deleted.

Message last modified on Jun 26, 2023 12:35PM

li...@gmail.com <li...@gmail.com> #9Jun 26, 2023 12:38PM

I wouldn't say this is fixed. If you add a back-callback in the activity which is lifecycle aware, and then background->foreground the app, the activity back-callback will be put on top of the callback pile. This leads to that any BackHandler in your composable will NOT be triggered.

The best workaround I have for now is to use the non-lifecycle aware function in the activity.

class MainActivity : FragmentActivity() {
    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)
        
        // open fragment which hoists the composables
        ...

        if (savedInstanceState == null) {
             onBackPressedDispatcher.addCallback(onBackPressedCallback = someBackHandling())  
            // onBackPressedDispatcher.addCallback(owner = this, onBackPressedCallback = someBackHandling)  // not this one
        }
    }

Message last modified on Jun 26, 2023 12:40PM

ho...@gmail.com <ho...@gmail.com> #10Jul 17, 2023 01:51PM

Comment has been deleted.

Message last modified on Jul 17, 2023 03:43PM

ho...@gmail.com <ho...@gmail.com> #11Jul 17, 2023 02:31PM

Comment has been deleted.

Message last modified on Jul 17, 2023 03:43PM

ho...@gmail.com <ho...@gmail.com> #12Jul 18, 2023 12:10PM

https://developer.android.com/jetpack/androidx/releases/navigation#2.7.0-beta01 :

Bug Fixes : NavHost in Navigation Compose now correctly intercepts system back calls even after the Activity has been STOPPED and RESUMED.

It works fine for me.

Message last modified on Jul 18, 2023 03:45PM

gi...@gmail.com <gi...@gmail.com> #13Sep 22, 2023 12:43PM

I can confirm this is still happening as mentioned in <li...@gmail.com> #9

va...@zedge.net <va...@zedge.net> #14Oct 11, 2023 02:25PM

Still reproduces.
In my case it works fine when the app is first ran, but my custom callback calls navController.popBackStack internally if it can't handle back press on its own. So, when I run the app and click back, everything works, but after I pop up all the Composables from the stack and return to the app, the custom callback is not called anymore.

il...@google.com <il...@google.com> #15Oct 11, 2023 04:45PM

Re comment#14 - please file a new issue with a project that reproduces your problem.

Note that you should never, ever be calling navController.popBackStack() in your own BackHandler as Navigation must be the only one handling its own back stack with the system back button so that Predictive Back works correctly in the future.

ja...@gopuff.com <ja...@gopuff.com> #16Oct 30, 2023 07:13PM

These changes broke our use case to override back handling in navigation library for closing the menu drawer. Please see more details in the issue I've reported.

ja...@sense.com <ja...@sense.com> #17Nov 14, 2024 05:36PM

I believe this is still an issue even without using NavHost like mentioned in comment #16. I filed a new issue here

IssueTracker

BackHandler not working correctly after activity resumes after being paused

Status Update

Description

Versions

Description

Steps to reproduce

Code to demonstrate the issue

Comments

jb...@google.com <jb...@google.com> #2Apr 25, 2023 11:08PM

[Deleted User] <[Deleted User]> #3Apr 25, 2023 11:16PM

il...@google.com <il...@google.com> Apr 26, 2023 11:44PM

jb...@google.com <jb...@google.com> #4Apr 27, 2023 12:26AM

ap...@google.com <ap...@google.com> #5Jun 1, 2023 12:50AM

il...@google.com <il...@google.com> #6Jun 1, 2023 05:00PM

pr...@google.com <pr...@google.com> #7Jun 8, 2023 01:31AM

an...@daresay.co <an...@daresay.co> #8Jun 26, 2023 12:35PM

li...@gmail.com <li...@gmail.com> #9Jun 26, 2023 12:38PM

ho...@gmail.com <ho...@gmail.com> #10Jul 17, 2023 01:51PM

ho...@gmail.com <ho...@gmail.com> #11Jul 17, 2023 02:31PM

ho...@gmail.com <ho...@gmail.com> #12Jul 18, 2023 12:10PM

gi...@gmail.com <gi...@gmail.com> #13Sep 22, 2023 12:43PM

va...@zedge.net <va...@zedge.net> #14Oct 11, 2023 02:25PM

il...@google.com <il...@google.com> #15Oct 11, 2023 04:45PM

ja...@gopuff.com <ja...@gopuff.com> #16Oct 30, 2023 07:13PM

ja...@sense.com <ja...@sense.com> #17Nov 14, 2024 05:36PM

Issue 279118447

Description

Versions

Description

Steps to reproduce

Code to demonstrate the issue

Issue summary

Comments

jb...@google.com <jb...@google.com> #2Apr 25, 2023 11:08PM

[Deleted User] <[Deleted User]> #3Apr 25, 2023 11:16PM

il...@google.com <il...@google.com> Apr 26, 2023 11:44PM

jb...@google.com <jb...@google.com> #4Apr 27, 2023 12:26AM

ap...@google.com <ap...@google.com> #5Jun 1, 2023 12:50AM

il...@google.com <il...@google.com> #6Jun 1, 2023 05:00PM

pr...@google.com <pr...@google.com> #7Jun 8, 2023 01:31AM

an...@daresay.co <an...@daresay.co> #8Jun 26, 2023 12:35PM

li...@gmail.com <li...@gmail.com> #9Jun 26, 2023 12:38PM

ho...@gmail.com <ho...@gmail.com> #10Jul 17, 2023 01:51PM

ho...@gmail.com <ho...@gmail.com> #11Jul 17, 2023 02:31PM

ho...@gmail.com <ho...@gmail.com> #12Jul 18, 2023 12:10PM

gi...@gmail.com <gi...@gmail.com> #13Sep 22, 2023 12:43PM

va...@zedge.net <va...@zedge.net> #14Oct 11, 2023 02:25PM

il...@google.com <il...@google.com> #15Oct 11, 2023 04:45PM

ja...@gopuff.com <ja...@gopuff.com> #16Oct 30, 2023 07:13PM

ja...@sense.com <ja...@sense.com> #17Nov 14, 2024 05:36PM

Add comment

Issue metadata