Skip to content

Android back button does not do navigator.pop() when using run_mojo #263

Closed

Description

@FlutterIssues

Issue by aghassemi
Thursday Nov 05, 2015 at 23:28 GMT
Originally opened as https://github.com/flutter/engine/issues/1973


I am running my MaterialApp in Mojo so it is using Mojo Shell instead of Sky Shell. This difference seems to be causing back button to exit the app rather than poping from navigator.

@abarth @Hixie

Activity

  1. FlutterIssues commented on Nov 9, 2015

    @FlutterIssues
    Author

    Comment by abarth
    Thursday Nov 05, 2015 at 23:36 GMT


    There's no back button integration in MojoShell on Android.

  2. FlutterIssues commented on Nov 9, 2015

    @FlutterIssues
    Author

    Comment by abarth
    Friday Nov 06, 2015 at 04:50 GMT


    @jamesr @j9brown Who's the right person to handle feature requests for MojoShell on Android?

  3. FlutterIssues commented on Nov 9, 2015

    @FlutterIssues
    Author

    Comment by jamesr
    Monday Nov 09, 2015 at 20:20 GMT


    @qsr is

  4. aghassemi commented on Nov 14, 2015

    @aghassemi
    Contributor

    @abarth Should https://github.com/domokit/mojo/issues/361 get integrated with Flutter or should the app listen for that event and pop from nav?

  5. abarth commented on Nov 14, 2015

    @abarth
    Contributor

    @aghassemi It's the same code to write either way. The simplest thing for the demo is to write the code in the app.

  6. aghassemi commented on Nov 15, 2015

    @aghassemi
    Contributor

    Thanks, SGTM.

  7. abarth commented on Nov 18, 2015

    @abarth
    Contributor

    I'm going to close this issue because the current plan is to do this in the slides app itself.

  8. github-actions commented on Sep 7, 2021

    @github-actions

    This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.

  9. locked as resolved and limited conversation to collaborators on Sep 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions