Unable to dismiss bottom drawer when predictive back gesture is on

[lazzzis]

Environment Information

• Package version(s): 0.1.46
• Android SDK version: Android T or above is required

Please provide a reproduction of the bug:

I am working on refactoring my app to support Android's predictive back gesture, which is expected to be enabled by default from Android 15.

To test it on Android 13 and 14, following these instructions:

1. Enable Develop options -> Predictive back animations
2. add android:enableOnBackInvokedCallback="true" in AndroidManifest.xml
3. Launch FluentUi.Demo -> V2 Components -> V2 Bottom Drawer -> Open Drawer
4. swipe back or press back button

Actual behavior:

Unable to dismiss the bottom drawer.

Expected behavior:

Swiping back should dismiss the bottom drawer.

Priorities and help requested:

Are you willing to submit a PR to fix?

Okay but need guidance. I know the reason why it fails is because currently ModalPopup relies on KEYCODE_BACK to handle back events.

fluentui-android/fluentui_core/src/main/java/com/microsoft/fluentui/compose/ModalPopup.kt

Line 213 in 4b780d4

if (event.keyCode == KeyEvent.KEYCODE_BACK) {

But per android's doc, once predictive back gesture is enabled, Android OS will not send KEYCODE_BACK when back button is pressed. The solution is to migrated to OnBackPressedDispatcher as suggested by Android's official guide. But due to potential complexities, I am not very confident to refactor ModalPopup without guidance.

Requested priority: High

[Dhruv-Mishra]

Hey @lazzzis I don't see the option to enable predictive back animations within the developer options on both my android 14 and android 15 emulated pixel devices, can you share which device you are using?

[lazzzis]

Android 14, Pixel 5a.

[microsoft-github-policy-service]

@Dhruv-Mishra

Gentle ping that this issue needs attention.

[Dhruv-Mishra]

Hey @lazzzis would you be comfortable scheduling a meeting about this issue?

[Dhruv-Mishra]

Hey @lazzzis , I have raised a PR to fix the same for bottomDrawers;

#744

Will close the issue after the next release