[Flutter 3.16.5][GetX-5_RC5] PopScope issue about getx HOT 12 OPEN

The Solution =

• Show AlertDialog when user Press back Button and GoBack or Stay on the same Page According to User Action ( Yes or No ) [ Logic ] ⇒

@override
  Widget build(BuildContext context) {
    // Back Navigation Logic while using AlertDialog
    return PopScope(
      canPop: false,
      onPopInvoked: (didPop) async {
        // if true then return nothing
        if (didPop) {
          return;
        }
        // if false then return AlertDialog Widget
        await showDialog(
          context: context,
          barrierDismissible: false,
          builder: (context) => AlertDialog(
            title: const Text('Do you want to Edit this ?'),
            actions: [
              OutlinedButton(
                onPressed: () {
                  // if user click on Yes then,

                  // First close the Dialog
                  Get.back();
                  // Then close the current page and go back
                  Get.back();
                },
                child: const Text('Yes'),
              ),
              OutlinedButton(
                onPressed: () {
                  // if user click on No then,

                  // Just close the dialog
                  Get.back();
                },
                child: const Text('No'),
              ),
            ],
          ),
        );
      },
      child: Scaffold();

======================================================================

Completely Tested on Production App.

It is Working Fine ! 👍

from getx.

yes, please! solutions?

from getx.

same problem

from getx.

I have the same problem.
When is it estimated that the issue can be resolved?

from getx.

+1 Any update?

from getx.

You can currently use BackButtonListener() as a temporary alternative, like this

BackButtonListener(
  onBackButtonPressed: () {
    var routePath = Get.currentRoute;
    if (routePath == '/') {
      if (_lastPressedAt == null ||
          DateTime.now().difference(_lastPressedAt!) >
              const Duration(seconds: 2)) {
        _lastPressedAt = DateTime.now();
        ScaffoldMessenger.of(context).showSnackBar(const SnackBar(
          content: Text("Press again to exit the program"),
        ));
        return Future.value(true);
      }
    } else {
      Navigator.pop(context);
      return Future.value(true);
    }
    SystemNavigator.pop();
    return Future.value(false);
  },
  child:Text("Hello,World!")
)

from getx.

You can currently use BackButtonListener() as a temporary alternative, like this

BackButtonListener(
  onBackButtonPressed: () {
    var routePath = Get.currentRoute;
    if (routePath == '/') {
      if (_lastPressedAt == null ||
          DateTime.now().difference(_lastPressedAt!) >
              const Duration(seconds: 2)) {
        _lastPressedAt = DateTime.now();
        ScaffoldMessenger.of(context).showSnackBar(const SnackBar(
          content: Text("Press again to exit the program"),
        ));
        return Future.value(true);
      }
    } else {
      Navigator.pop(context);
      return Future.value(true);
    }
    SystemNavigator.pop();
    return Future.value(false);
  },
  child:Text("Hello,World!")
)

The BackButtonListener adds more problem when you have two of them.

Eg.

Your home screen has BottomNavigationBar, so you put a BackButtonListener to check if the user is on the 1st tab, if yes, then exit, else change the current tab to 1st one.

This works, however, if you have a popup open which needs to block the back button, you cannot rely on BackButtonListener as both the listeners will be triggered.

The idea of supporting the PopScope is to have the support for Predictive Back Gesture in Android 13+

You can currently enable this feature from the Developer Options in Android 13+

from getx.

I've also had this problem after popScope, but I'm currently not using two BackButtonListeners. This is indeed a problem.

from getx.

Same problem here.

from getx.

Related to flutter/flutter#138614

from getx.

Related to flutter/flutter#138614

Thanks for your time to look into the issue.

However, even if the WillPopScope is retained, can we fix the PopScope in some way ? 🫣

This can be the low priority issue as I understand you are highly occupied with the new GetX update.

from getx.

GetX 4.6.6 does not seem to have this problem and PopScope can be used correctly

from getx.