(In reply to Bob from comment #47) > As an aside, I think it actually might be possible to fix/avoid this on Android 13 by [selectively enabling](https://stackoverflow.com/questions/63621311) the `enableOnBackInvokedCallback` flag only on API34 (in a similar way to how Fenix already has `API28`/`underAPI28` bools defined). Enabling that flag only on API34+ sounds like a great approach indeed! And we now have bug 1944817 to which such a patch can be linked. I assume you want to work on this? Let me know if not and we can find another owner.
Bug 1932300 Comment 49 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Bob from comment #47) > As an aside, I think it actually might be possible to fix/avoid this on Android 13 by [selectively enabling](https://stackoverflow.com/questions/63621311) the `enableOnBackInvokedCallback` flag only on API34 (in a similar way to how Fenix already has `API28`/`underAPI28` bools defined). Enabling that flag only on API34+ sounds like a great approach indeed! And we now have bug 1944817 to which such a patch can be linked. I assume you want to work on this? Let me know if not and we can find another owner. (In reply to Bob from comment #47) > Unfortunately, I don't have an Android 13 device anywhere to test. And turning this off will likely reintroduce bug 1898059 on Android 13 (it's a bit unclear to me from the comments/review whether that bug only affected 14+ or also 13) Testing on an emulator myself I don't see the issue from bug 1898059 if `enableOnBackInvokedCallback` is disabled. Can request QA's help for a prevalidation of the patch on physical Android 13 devices before landing to be extra safe.