Back key not detected on Android Gesture Navigation

britzl · January 7, 2025, 2:56pm

I wonder if we broke something during glfw migration? It is supposed to work correctly with gestures:

github.com/defold/defold

Added back gesture support for Android 13

defold:dev ← defold:issue-6821

opened 11:27AM - 19 Apr 23 UTC

AGulev

+58 -40

Android 13 doesn't support Back button anymore. Instead, it uses back gesture. T…his fix added support for this gesture in the engine using the same "Back" event in the input bindings. More info is available in t[he official Android documentation](https://developer.android.com/guide/navigation/predictive-back-gesture#migrate-app). >⚠️ `AndroidManifes.xml` updated with new flag `android:enableOnBackInvokedCallback="true"` for the `<application>` tag. If you use your own manifest, make sure you apply the same changes. Fix https://github.com/defold/defold/issues/6821 ## PR checklist * [x] Code * [ ] Add engine and/or editor unit tests. * [x] New and changed code follows the overall code style of existing code * [x] Add comments where needed * [ ] Documentation * [ ] Make sure that API documentation is updated in code comments * [ ] Make sure that manuals are updated (in github.com/defold/doc) * [ ] Prepare pull request and affected issue for automatic release notes generator * [x] Pull request - Write a message that explains what this pull request does. What was the problem? How was it solved? What are the changes to APIs or the new APIs introduced? This message will be used in the generated release notes. Make sure it is well written and understandable for a user of Defold. * [x] Pull request - Write a pull request title that in a sentence summarises what the pull request does. Do not include "Issue-1234 ..." in the title. This text will be used in the generated release notes. * [x] Pull request - Link the pull request to the issue(s) it is closing. Use on of the [approved closing keywords](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue). * [x] Affected issue - Assign the issue to a project. Do not assign the pull request to a project if there is an issue which the pull request closes. * [ ] Affected issue - Assign the "breaking change" label to the issue if introducing a breaking change. * [ ] Affected issue - Assign the "skip release notes" is the issue should not be included in the generated release notes.

Ping @AGulev and @jhonny.goransson