Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Post History

75%
+4 −0
Q&A How do I add functionality to the back button?

TL;DR : end your callback with a call to finish(). According to this article, addCallback really does add a callback. However, the way Android handles these callbacks is this: Iterator<OnBack...

posted 1y ago by FractionalRadix‭  ·  edited 1y ago by FractionalRadix‭

Answer
#2: Post edited by user avatar FractionalRadix‭ · 2023-07-12T20:34:24Z (over 1 year ago)
  • TL;DR : end your callback with a call to `finish()`.
  • According to [this article](https://proandroiddev.com/handling-back-press-in-android-13-the-correct-way-be43e0ad877a), `addCallback` really does _add_ a callback. However, the way Android handles these callbacks is this:
  • Iterator<OnBackPressedCallback> iterator =
  • mOnBackPressedCallbacks.descendingIterator();
  • while (iterator.hasNext()) {
  • OnBackPressedCallback callback = iterator.next();
  • if (callback.isEnabled()) {
  • callback.handleOnBackPressed();
  • return;
  • }
  • }
  • In other words, as soon as a callback is enabled, that callback is executed, and the rest are ignored.
  • This leads to a counterintuitive situation where having even a single callback enabled, causes that callback to be executed _instead_ of the code that actually takes you back to a previous Activity!
  • This is intentional. The [official Android guide](https://developer.android.com/guide/navigation/custom-back#activity_onbackpressed) gives an example of overriding the "Back" behavior where the developer doesn't want the normal "Back" behavior to take place. The reason seems to be that this new way of working, supports Android's [Predictive Back Gesture](https://developer.android.com/guide/navigation/custom-back/predictive-back-gesture).
  • The simplest solution is to end your callback with a call to `finish()`. Note that this will call `onDestroy()` for your Activity.
  • If that is not an option, you may be able to make calls on the `onBackInvokedDispatcher` directly, rather than using the `onBackPressedDispatcher`. As of this writing, I have not yet done that, and it seems a rather dirty way of getting what you want.
  • Further sources used: ["onBackPressed() deprecated, What is the alternative?"](https://stackoverflow.com/q/72634225/812149) on Stack Overflow.
  • TL;DR : end your callback with a call to `finish()`.
  • According to [this article](https://proandroiddev.com/handling-back-press-in-android-13-the-correct-way-be43e0ad877a), `addCallback` really does _add_ a callback. However, the way Android handles these callbacks is this:
  • Iterator<OnBackPressedCallback> iterator =
  • mOnBackPressedCallbacks.descendingIterator();
  • while (iterator.hasNext()) {
  • OnBackPressedCallback callback = iterator.next();
  • if (callback.isEnabled()) {
  • callback.handleOnBackPressed();
  • return;
  • }
  • }
  • In other words, as soon as a callback is enabled, that callback will be the one to be executed, and any callbacks added earlier will be ignored.
  • This leads to a counterintuitive situation where having even a single callback enabled, causes that callback to be executed _instead_ of the code that actually takes you back to a previous Activity!
  • This is intentional. The [official Android guide](https://developer.android.com/guide/navigation/custom-back#activity_onbackpressed) gives an example of overriding the "Back" behavior where the developer doesn't want the normal "Back" behavior to take place. The reason seems to be that this new way of working, supports Android's [Predictive Back Gesture](https://developer.android.com/guide/navigation/custom-back/predictive-back-gesture).
  • The simplest solution is to end your callback with a call to `finish()`. Note that this will call `onDestroy()` for your Activity.
  • If that is not an option, you may be able to make calls on the `onBackInvokedDispatcher` directly, rather than using the `onBackPressedDispatcher`. As of this writing, I have not yet done that, and it seems a rather dirty way of getting what you want.
  • Further sources used: ["onBackPressed() deprecated, What is the alternative?"](https://stackoverflow.com/q/72634225/812149) on Stack Overflow.
#1: Initial revision by user avatar FractionalRadix‭ · 2023-07-12T20:33:31Z (over 1 year ago)
TL;DR : end your callback with a call to `finish()`.

According to [this article](https://proandroiddev.com/handling-back-press-in-android-13-the-correct-way-be43e0ad877a), `addCallback` really does _add_ a callback. However, the way Android handles these callbacks is this:

     Iterator<OnBackPressedCallback> iterator =
              mOnBackPressedCallbacks.descendingIterator();
      while (iterator.hasNext()) {
          OnBackPressedCallback callback = iterator.next();
          if (callback.isEnabled()) {
              callback.handleOnBackPressed();
              return;
          }
      }

In other words, as soon as a callback is enabled, that callback is executed, and the rest are ignored.   

This leads to a counterintuitive situation where having even a single callback enabled, causes that callback to be executed _instead_ of the code that actually takes you back to a previous Activity!  
This is intentional. The [official Android guide](https://developer.android.com/guide/navigation/custom-back#activity_onbackpressed) gives an example of overriding the "Back" behavior where the developer doesn't want the normal "Back" behavior to take place. The reason seems to be that this new way of working, supports Android's [Predictive Back Gesture](https://developer.android.com/guide/navigation/custom-back/predictive-back-gesture).  

The simplest solution is to end your callback with a call to `finish()`. Note that this will call `onDestroy()` for your Activity.  

If that is not an option, you may be able to make calls on the `onBackInvokedDispatcher` directly, rather than using the `onBackPressedDispatcher`. As of this writing, I have not yet done that, and it seems a rather dirty way of getting what you want.  

Further sources used: ["onBackPressed() deprecated, What is the alternative?"](https://stackoverflow.com/q/72634225/812149) on Stack Overflow.