[CupertinoPageRoute] Gestures don't respond when clicking immediately after swiping back #73026

yaminet1024 · 2020-12-28T09:28:50Z

The problem is that after I use cupertionPageroute, when I swipe back to the previous page on iOS device, there is a high probability that the first time I click on the content of the previous page, nothing happens until I click twice, especially when you are halfway through the slide. Let go, and then quickly click on the previous page. The online business here is very seriously affected.

video

2020-12-285.26.13.mov

flutter doctor

Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel unknown, 1.22.4, on macOS 11.1 20C69 darwin-x64, locale zh-Hans-CN)
[!] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
! Some Android licenses not accepted. To resolve this, run: flutter doctor --android-licenses
[✓] Xcode - develop for iOS and macOS (Xcode 12.3)
[!] Android Studio (version 4.1)
✗ Flutter plugin not installed; this adds Flutter specific functionality.
✗ Dart plugin not installed; this adds Dart specific functionality.
[✓] VS Code (version 1.52.1)
[✓] Connected device (2 available)

! Doctor found issues in 2 categories.

this is the mini example

main.dart

import 'package:flutter/material.dart';
import 'package:trace_startup/page.dart';

void main() {
  runApp(MyApp());
}

class MyApp extends StatelessWidget {
  // This widget is the root of your application.
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        primarySwatch: Colors.blue,
        visualDensity: VisualDensity.adaptivePlatformDensity,
      ),
      home: MyHomePage(title: 'Flutter Demo Home Page'),
    );
  }
}

class MyHomePage extends StatefulWidget {
  MyHomePage({Key key, this.title}) : super(key: key);

  final String title;

  @override
  _MyHomePageState createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text(widget.title),
      ),
      body: FlatButton(
        color: Colors.blue,
        onPressed: () {
          Navigator.push(context, CupertinoPageRoute(builder: (context) {
            return SecondPage();
          }));
        },
        child: Container(
          height: double.infinity,
          width: double.infinity,
          child: Center(
            child: Text(
              'push new page',
            ),
          ),
        ),
      ),
    );
  }
}

page.dart

import 'package:flutter/cupertino.dart';
import 'package:flutter/material.dart';

class SecondPage extends StatelessWidget{
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(title: Text("second page"),),
      body: Center(child: Text("second page"),),
    );
  }

}

The text was updated successfully, but these errors were encountered:

darshankawar · 2020-12-28T11:32:47Z

Tried your code sample on iPhoneSE simulator, but didn't notice the issue. I was able to swipe from second screen to first properly.

73026.mov

flutter doctor -v


[✓] Flutter (Channel stable, 1.22.5, on Mac OS X 10.15.4 19E2269 darwin-x64,
    locale en-IN)
    • Flutter version 1.22.5 at /Users/dhs/documents/Fluttersdk/flutter
    • Framework revision 7891006299 (3 weeks ago), 2020-12-10 11:54:40 -0800
    • Engine revision ae90085a84
    • Dart version 2.10.4

 
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.0)
    • Android SDK at /Users/dhs/Library/Android/sdk
    • Platform android-30, build-tools 30.0.0
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 12.0.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.0.1, Build version 12A7300
    • CocoaPods version 1.9.3

[✓] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 46.0.2
    • Dart plugin version 193.7361
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6222593)

[✓] VS Code (version 1.51.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.16.0

[✓] Connected device (2 available)
    • sdk gphone x86 arm (mobile)         • emulator-5554
      • android-x86 • Android 11 (API 30) (emulator)
    • iPhone SE (2nd generation) (mobile) • 6C85835D-FBFD-4AB3-8DE8-B4FAD35E5367
      • ios         • com.apple.CoreSimulator.SimRuntime.iOS-14-0 (simulator)

• No issues found!

Do you see the same behavior on physical device also ?

yaminet1024 · 2020-12-28T12:11:30Z

Tried your code sample on iPhoneSE simulator, but didn't notice the issue. I was able to swipe from second screen to first properly.

I think your sliding range is too large. Try to release it when sliding to the middle, or use a real machine to simulate the side-slip effect, it is very easy to appear

yaminet1024 · 2020-12-28T12:33:34Z

Tried your code sample on iPhoneSE simulator, but didn't notice the issue. I was able to swipe from second screen to first properly.

I think your sliding range is too large. Try to release it when sliding to the middle, or use a real machine to simulate the side-slip effect, it is very easy to appear。

video.17.mov

darshankawar · 2020-12-28T13:04:26Z

flutter doctor -v

[✓] Flutter (Channel stable, 1.22.5, on Mac OS X 10.15.4 19E2269 darwin-x64,
    locale en-IN)
    • Flutter version 1.22.5 at /Users/dhs/documents/Fluttersdk/flutter
    • Framework revision 7891006299 (3 weeks ago), 2020-12-10 11:54:40 -0800
    • Engine revision ae90085a84
    • Dart version 2.10.4

 
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.0)
    • Android SDK at /Users/dhs/Library/Android/sdk
    • Platform android-30, build-tools 30.0.0
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 12.0.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.0.1, Build version 12A7300
    • CocoaPods version 1.9.3

[✓] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 46.0.2
    • Dart plugin version 193.7361
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6222593)

[✓] VS Code (version 1.51.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.16.0

[✓] Connected device (2 available)
    • sdk gphone x86 arm (mobile)         • emulator-5554
      • android-x86 • Android 11 (API 30) (emulator)
    • iPhone SE (2nd generation) (mobile) • 6C85835D-FBFD-4AB3-8DE8-B4FAD35E5367
      • ios         • com.apple.CoreSimulator.SimRuntime.iOS-14-0 (simulator)

• No issues found!

justinmc · 2020-12-28T17:26:04Z

CC @xster

chunhtai · 2020-12-28T19:04:14Z

cc @dkwingsmt

TahaTesser · 2021-03-08T15:06:34Z

flutter doctor -v

[✓] Flutter (Channel stable, 2.0.1, on macOS 11.2.2 20D80 darwin-x64, locale en-GB)
    • Flutter version 2.0.1 at /Users/tahatesser/Code/flutter_stable
    • Framework revision c5a4b4029c (4 days ago), 2021-03-04 09:47:48 -0800
    • Engine revision 40441def69
    • Dart version 2.12.0

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Volumes/Extreme/SDK
    • Platform android-30, build-tools 30.0.3
    • ANDROID_HOME = /Volumes/Extreme/SDK
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Volumes/Extreme/Xcode.app/Contents/Developer
    • Xcode 12.4, Build version 12D4e
    • CocoaPods version 1.10.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)

[✓] VS Code (version 1.54.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.20.0

[✓] Connected device (3 available)
    • Taha’s iPhone (mobile) • 00008020-001059882212002E • ios            • iOS 14.4
    • macOS (desktop)        • macos                     • darwin-x64     • macOS 11.2.2 20D80 darwin-x64
    • Chrome (web)           • chrome                    • web-javascript • Google Chrome 88.0.4324.192

• No issues found!

[✓] Flutter (Channel master, 2.1.0-11.0.pre.145, on macOS 11.2.2 20D80 darwin-x64, locale en-GB)
    • Flutter version 2.1.0-11.0.pre.145 at /Users/tahatesser/Code/flutter_master
    • Framework revision a0ba646408 (3 days ago), 2021-03-05 22:09:03 -0500
    • Engine revision f751d04fa0
    • Dart version 2.13.0 (build 2.13.0-107.0.dev)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Volumes/Extreme/SDK
    • Platform android-30, build-tools 30.0.3
    • ANDROID_HOME = /Volumes/Extreme/SDK
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Volumes/Extreme/Xcode.app/Contents/Developer
    • Xcode 12.4, Build version 12D4e
    • CocoaPods version 1.10.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)

[✓] VS Code (version 1.54.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.20.0

[✓] Connected device (3 available)
    • Taha’s iPhone (mobile) • 00008020-001059882212002E • ios            • iOS 14.4
    • macOS (desktop)        • macos                     • darwin-x64     • macOS 11.2.2 20D80 darwin-x64
    • Chrome (web)           • chrome                    • web-javascript • Google Chrome 88.0.4324.192

• No issues found!

proformance · 2021-03-09T18:35:59Z

I can confirm this is an issue.

I've recorded a video that shows different types opening&closenings: https://vimeo.com/521522681

First attempt I release it to the far right, notice how it's getting disposed immediately.
Second attempt I release it to the left, pay attention to how long it takes until it gets disposed
Third attempt, I release it to the left, now I also tap before it has been disposed, which shows how it is unresponsive. Only after it has been disposed it will be possible to open the page again.

I've modified the original minimally to make it stateful (and hence have the dispose function)

Expand code here

import 'package:flutter/cupertino.dart';
import 'package:flutter/material.dart';

class SecondPage extends StatefulWidget {
  @override
  State<StatefulWidget> createState() => SecondPageState();
}

class SecondPageState extends State<SecondPage> {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text("second page"),
      ),
      body: Center(
        child: Text("second page"),
      ),
    );
  }

  @override
  void dispose() {
    print('disposing page');
    super.dispose();
  }
}

import 'package:flutter/cupertino.dart';
import 'package:flutter/material.dart';

void main() {
  runApp(MyApp());
}

class MyApp extends StatelessWidget {
  // This widget is the root of your application.
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        primarySwatch: Colors.blue,
        visualDensity: VisualDensity.adaptivePlatformDensity,
      ),
      home: MyHomePage(title: 'Flutter Demo Home Page'),
    );
  }
}

class MyHomePage extends StatefulWidget {
  MyHomePage({Key key, this.title}) : super(key: key);

  final String title;

  @override
  _MyHomePageState createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text(widget.title),
      ),
      body: FlatButton(
        color: Colors.blue,
        onPressed: () {
          print('opening page');
          Navigator.push(context, CupertinoPageRoute(builder: (context) {
            return SecondPage();
          }));
        },
        child: Container(
          height: double.infinity,
          width: double.infinity,
          child: Center(
            child: Text(
              'push new page',
            ),
          ),
        ),
      ),
    );
  }
}

flutter doctor -v

[✓] Flutter (Channel beta, 1.26.0-17.8.pre, on macOS 11.2.2 20D80 darwin-x64, locale en-GB) • Flutter version 1.26.0-17.8.pre at /Users/mariusgrimstad/dev/flutter • Framework revision 044f2cf (13 days ago), 2021-02-24 13:02:05 -0800 • Engine revision 042c82b • Dart version 2.12.0 (build 2.12.0-259.16.beta)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
• Android SDK at /Users/mariusgrimstad/Library/Android/sdk
• Platform android-30, build-tools 30.0.2
• Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
• All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS
• Xcode at /Applications/Xcode.app/Contents/Developer
• Xcode 12.4, Build version 12D4e
• CocoaPods version 1.10.1

[✓] Chrome - develop for the web
• Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.0)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin version 49.0.2
• Dart plugin version 193.7547
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)

[✓] VS Code (version 1.53.2)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension version 3.20.0

[✓] Connected device (2 available)
• iPhone 12 Pro Max (mobile) • 2AB03A37-D1B2-463E-A73E-E1E16FB7124A • ios •
com.apple.CoreSimulator.SimRuntime.iOS-14-4 (simulator)
• Chrome (web) • chrome • web-javascript •
Google Chrome 88.0.4324.192

• No issues found!

proformance · 2021-04-13T20:09:51Z

Looking at it more in detail it seems like animation curve combined with the inner workings of route might be the problem here.

https://github.com/flutter/flutter/blob/master/packages/flutter/lib/src/cupertino/route.dart#L735

Currently the dismissal animation is using the curve Curves.fastLinearToSlowEaseIn

I added some debug traces to see the animation-value and timestamps, here's a snippet how it looks close to the end of the animation.

...
flutter: buildTransitions 0.013482164725324042 (1618342815382) <---  barely visible as only 1% of the width is shown
flutter: buildTransitions 0.010625395290166484 (1618342815399)
flutter: buildTransitions 0.008203684573317105 (1618342815415)
flutter: buildTransitions 0.006376271156842028 (1618342815432)
flutter: buildTransitions 0.004842631100606232 (1618342815448)
flutter: buildTransitions 0.003644510584527083 (1618342815465)
flutter: buildTransitions 0.0027178166513320834 (1618342815482)
flutter: buildTransitions 0.0019632494060380923 (1618342815498)
flutter: buildTransitions 0.001398682602685053 (1618342815515)
flutter: buildTransitions 0.0009542743748859328 (1618342815532)
flutter: buildTransitions 0.0006366329552504046 (1618342815548)
flutter: buildTransitions 0.00039868855001279346 (1618342815565)
flutter: buildTransitions 0.00023982897851249074 (1618342815582)
flutter: buildTransitions 0.00013001372356491459 (1618342815599)
flutter: buildTransitions 0.00006018844980637539 (1618342815615)
flutter: buildTransitions 0.000023578998342599355 (1618342815632)
flutter: buildTransitions 0.000005529384273339488 (1618342815648)
flutter: buildTransitions 4.4712767222065963e-7 (1618342815665)   <--- animation will now stop as it reached ~0
flutter: AnimationStatusListener->AnimationStatus.dismissed (1618342815684)  <--- status has changed, will trigger pop

As you can see, the value is almost 0 ( == barely visible at the very right edge) for about 300ms before the AnimationStatus is equal to dismissed. This means it will look like it is popped, but is still there.

Only when the status has changed to AnimationStatus.dismissed, it will call stopUserGesture
https://github.com/flutter/flutter/blob/master/packages/flutter/lib/src/cupertino/route.dart#L773

Digging further it turns out stopGesture actually blocks user-input.
https://github.com/flutter/flutter/blob/master/packages/flutter/lib/src/widgets/routes.dart#L832

This means it will by the current design block any input for some time (even though the user is not seeing anything of the previous modal) before the user can interact again. The time will depend on how far to the right you drop it, so if you drop it far to the right it will barely affect the user, but if you make a quick swipe-to-dismiss on the left side on the screen, the user will be heavily affected.

proformance · 2021-04-14T06:38:43Z

@chunhtai @TahaTesser @gspencergoog

I found that this issue was the reason for blocking the user-input during the userGesture. I tried to remove this line and can confirm the feeling was much smoother as a new tap on the previous page would respond immediately. (However with some side-effects afterwards of course). Do you have any suggestion on how to solve this in another way where it doesn't have to be blocked?

Currently the feeling is not smooth as some taps are not responding, specially when using an actual device.

mm-public-tx · 2021-11-05T03:31:45Z

@xster

ConProgramming · 2022-10-06T01:41:00Z

thanks for @proformance modification, problem sovled(but maybe other things break).

For anyone can't find related line inhttps://github.com/flutter/flutter/blob/master/packages/flutter/lib/src/widgets/routes.dart

// before modification
  bool get _shouldIgnoreFocusRequest {
    return widget.route.animation?.status == AnimationStatus.reverse ||
      (widget.route.navigator?.userGestureInProgress ?? false);
  }
// after modification
  bool get _shouldIgnoreFocusRequest {
    return widget.route.animation?.status == AnimationStatus.reverse; // ||
      //(widget.route.navigator?.userGestureInProgress ?? false);
  }

I believe it's not CupertinoPageRoute specific either, because this fixed the issue for me.

ConProgramming · 2022-10-06T02:54:21Z

To be clear: Still very much an issue. The patch above made it usable, but, for example when opening a different route while the current one is closing, there's a weird jump in the animation. Where it previously wouldn't have responded at all it now does respond, but with a weird animation jump

TahaTesser · 2022-10-06T07:20:23Z

To be clear: Still very much an issue. The patch above made it usable, but, for example when opening a different route while the current one is closing, there's a weird jump in the animation. Where it previously wouldn't have responded at all it now does respond, but with a weird animation jump

That's a great observation, given the sample reproduces the issue when swiping back with CupertinoPageRoute, this description is useful for anyone running into this issue or when trying to fix it.

FantaZZ · 2022-11-07T15:32:57Z

Has any news ?

justinmc · 2022-11-07T19:05:00Z

CC @MitchellGoodwin

MitchellGoodwin · 2022-11-07T19:10:45Z

Sorry we haven't gotten to this yet. This isn't actively being worked on yet, but it is high on my list once I finish a few other issues, unless someone else gets to it first.

xhzq233 · 2023-06-08T13:47:10Z

any updates?

flutter-triage-bot · 2023-07-08T02:34:35Z

This issue is assigned but has had no recent status updates. Please consider unassigning this issue if it is not going to be addressed in the near future. This allows people to have a clearer picture of what work is actually planned. Thanks!

MitchellGoodwin · 2023-08-18T22:02:58Z

I'm not currently working on this, but I'm leaving it assigned as this, and other route transition issues are immediate on my list after I finish the current larger issues on my queue. If someone wants to take a crack at it before then, feel free to submit a PR or reach out.

flutter-triage-bot · 2024-01-05T22:07:42Z

This issue is assigned to @MitchellGoodwin but has had no recent status updates. Please consider unassigning this issue if it is not going to be addressed in the near future. This allows people to have a clearer picture of what work is actually planned. Thanks!

sjamr10 · 2024-05-15T20:38:40Z

I'm facing the same issue with MaterialPageRoute, if you wait a little bit it works fine but if you tap something immediately after going back it doesn't work.
And it seems to only affect iOS.

darshankawar added in triage Presently being triaged by the triage team waiting for customer response The Flutter team cannot make further progress on this issue until the original reporter responds labels Dec 28, 2020

no-response bot removed the waiting for customer response The Flutter team cannot make further progress on this issue until the original reporter responds label Dec 28, 2020

chunhtai added the f: gestures flutter/packages/flutter/gestures repository. label Dec 29, 2020

jmagman added this to Awaiting triage in iOS Platform - Cupertino widget review Jan 21, 2021

TomiCode mentioned this issue Mar 8, 2021

On navigation back swipe, widgets not receiving touch events #77592

Closed

TahaTesser added found in release: 2.0 Found to occur in 2.0 found in release: 2.1 Found to occur in 2.1 c: performance Relates to speed or footprint issues (see "perf:" labels) labels Mar 8, 2021

proformance mentioned this issue Mar 9, 2021

Time of disposal after swipe depends on where it is released JonasWanke/swipeable_page_route#9

Open

XtrangeV mentioned this issue Nov 3, 2021

Is the second half of the animation curve fastLinearToSlowEaseIn too slow #92978

Open

TahaTesser added found in release: 3.4 Found to occur in 3.4 and removed platform-ios iOS applications specifically found in release: 1.22 Found to occur in 1.22 found in release: 2.0 Found to occur in 2.0 found in release: 2.1 Found to occur in 2.1 passed first triage labels Oct 5, 2022

MitchellGoodwin self-assigned this Dec 5, 2022

MitchellGoodwin mentioned this issue Dec 7, 2022

Fix gestures not responding on swipe back #116694

Closed

8 tasks

flutter-triage-bot bot added multiteam-retriage-candidate team-design Owned by Design Languages team triaged-design Triaged by Design Languages team and removed triaged-design Triaged by Design Languages team labels Jul 8, 2023

flutter-triage-bot bot added the ⏳ Bot is counting down the days until it unassigns the issue label Jul 30, 2023

MitchellGoodwin added P2 Important issues not at the top of the work list triaged-design Triaged by Design Languages team labels Aug 18, 2023

flutter-triage-bot bot removed the ⏳ Bot is counting down the days until it unassigns the issue label Aug 18, 2023

flutter-triage-bot bot added the ⏳ Bot is counting down the days until it unassigns the issue label Jan 5, 2024

Hixie removed the multiteam-retriage-candidate label Mar 6, 2024

flutter-triage-bot bot removed the ⏳ Bot is counting down the days until it unassigns the issue label Mar 6, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[CupertinoPageRoute] Gestures don't respond when clicking immediately after swiping back #73026

[CupertinoPageRoute] Gestures don't respond when clicking immediately after swiping back #73026

yaminet1024 commented Dec 28, 2020

darshankawar commented Dec 28, 2020 •

edited

yaminet1024 commented Dec 28, 2020

yaminet1024 commented Dec 28, 2020

darshankawar commented Dec 28, 2020

justinmc commented Dec 28, 2020

chunhtai commented Dec 28, 2020

TahaTesser commented Mar 8, 2021

proformance commented Mar 9, 2021

proformance commented Apr 13, 2021

proformance commented Apr 14, 2021

mm-public-tx commented Nov 5, 2021

ConProgramming commented Oct 6, 2022

ConProgramming commented Oct 6, 2022

TahaTesser commented Oct 6, 2022

FantaZZ commented Nov 7, 2022

justinmc commented Nov 7, 2022

MitchellGoodwin commented Nov 7, 2022

xhzq233 commented Jun 8, 2023

flutter-triage-bot bot commented Jul 8, 2023

MitchellGoodwin commented Aug 18, 2023

flutter-triage-bot bot commented Jan 5, 2024

sjamr10 commented May 15, 2024 •

edited

[CupertinoPageRoute] Gestures don't respond when clicking immediately after swiping back #73026

[CupertinoPageRoute] Gestures don't respond when clicking immediately after swiping back #73026

Comments

yaminet1024 commented Dec 28, 2020

video

flutter doctor

this is the mini example

darshankawar commented Dec 28, 2020 • edited

yaminet1024 commented Dec 28, 2020

yaminet1024 commented Dec 28, 2020

darshankawar commented Dec 28, 2020

justinmc commented Dec 28, 2020

chunhtai commented Dec 28, 2020

TahaTesser commented Mar 8, 2021

proformance commented Mar 9, 2021

proformance commented Apr 13, 2021

proformance commented Apr 14, 2021

mm-public-tx commented Nov 5, 2021

ConProgramming commented Oct 6, 2022

ConProgramming commented Oct 6, 2022

TahaTesser commented Oct 6, 2022

FantaZZ commented Nov 7, 2022

justinmc commented Nov 7, 2022

MitchellGoodwin commented Nov 7, 2022

xhzq233 commented Jun 8, 2023

flutter-triage-bot bot commented Jul 8, 2023

MitchellGoodwin commented Aug 18, 2023

flutter-triage-bot bot commented Jan 5, 2024

sjamr10 commented May 15, 2024 • edited

darshankawar commented Dec 28, 2020 •

edited

sjamr10 commented May 15, 2024 •

edited