[Bug]: Severe UI Jank & Full Navigation Stack Rebuild on TextField Focus (Un-isolated MediaQuery/Scaffold Binding)

[saswat216]

Can we access your project?

• I give permission for members of the FlutterFlow team to access and test my project for the sole purpose of investigating this issue.

Current Behavior

We are experiencing a critical performance blocker: whenever a user focuses on any TextField across our major data-entry forms, the 300ms device keyboard slide animation triggers a complete, frame-by-frame rebuild of the entire page and navigation stack. This causes massive UI jank and severe SurfaceFrame::Submit frame drops, effectively freezing the app.

Initially, we suspected this was isolated to a RichText component inside a Bottom Sheet. However, we are now experiencing the exact same massive rebuild cycle on our standard, full-screen pages (add_fuel_log_page_basic, add_fuel_log_page_pro, and add_service_log_page).

After profiling with Flutter DevTools, it is clear that the rapid viewInsets changes from the keyboard animation are forcing every widget on these complex pages to rebuild on every frame. This points to a broader framework-level routing or MediaQuery binding issue in how FlutterFlow generates code for forms and Scaffolds.

This happens despite the following strict optimizations we have already applied:

• Disabled "Resize to avoid bottom inset" on the root Scaffolds.

• Avoided all percentage-based sizing to prevent accidental MediaQuery.of(context).size rebuilds.

Expected Behavior

Focusing a TextField and triggering the keyboard should smoothly animate the keyboard into view. It should not force the entire navigation stack and all widgets on a complex page to recalculate their layout on every frame, especially when keyboard avoidance features are explicitly turned off. if a form Page is 3 navigation deep then the textfield focus (when keyboard appears) should not rebuild the entire navigation stack.

Steps to Reproduce

Reproduce from Blank:

create a form field page and put it in a multiple navigation deep.

E.g, Home page (add multiple container/ images/buttons or widgets)--> Page 1 (same add widgets not blank) --> Page 2 (same add widgets not blank) --> Page 3 with text fields

Now tap Textfields in this Page 3, Observe the DevTools performance timeline

Reproduce in Our App:

https://app.flutterflow.io/project/ridex-7i2xb8?tab=pageSelector&page=AddFuelLog_Page_basic

https://app.flutterflow.io/project/ridex-7i2xb8?tab=pageSelector&page=AddFuelLog_Page_pro

https://app.flutterflow.io/project/ridex-7i2xb8?tab=pageSelector&page=AddServiceLog_Page

https://app.flutterflow.io/project/ridex-7i2xb8?tab=pageSelector&component=addTripExpense_btmSheet

Navigate to a complex form page built in FlutterFlow (e.g., our Add Trip expense Page OR Add Fuel Log Basic OR Add Service Log pages).

Ensure "Resize to avoid bottom inset" is disabled on the root Scaffold.

Run the app on a physical device and connect Flutter DevTools.

Tap any TextField to open the keyboard.

Result: Observe the DevTools performance timeline showing severe SurfaceFrame::Submit delays and a massive widget tree rebuild tied to the keyboard's viewInsets animation.

Note: if you are not able to compile the code and finding errors in the "Fuel Log History Page", in code editor of the page Search "RowList" (2 result will be found) and replace with "Row". (this is also a flutterflow code generation Bug)

Reproducible from Blank

• The steps to reproduce above start from a blank project.

Bug Report Code (Required)

ITEehsrl25NJtb0D1anyLfpoqwMwGkQ5a7sviu5+FBQaI+LmO5kAZsj7akpvcuqHfHw3MWCYhkYfw82Kj9/pLMAVCy6ufaZ4/rtXUxDicGKgRJSOEs+oWHwkEfNUIUC41qSVux4kItdvW1Ii7Uy2N+q+b3qCf9qOYwx5e6fDbOY=

Visual documentation

This image shows the Dev tools Performance timeline when UI jank happens on TextField Focus in Add trip expense Bottom sheet.

Environment

- FlutterFlow version: 6.6.9
- Platform: Android & Ios
- Browser name and version: on physical Android device and Ios Simulator (iphone 17)
- Operating system and version affected: Android 15 and ios 26.1

Additional Information

Since this is a release-blocking performance issue across our core app features, we urgently request this bug to be resolved or anything I am doing wrong here then an in-person review or a direct technical call with a FlutterFlow engineer. We need expert help to profile our specific project structure and find a definitive framework-level workaround.

[Juansarmi]

Hi there!

Sorry to hear you're running into this issue. I’ve tried to reproduce it on my end but haven’t had any luck so far.

Could you let me know which platform and operating system you’re using with FlutterFlow, as well as the version you’re currently on?

If you’re able to recreate the issue in a new blank project, that would really help speed things up on our side.

Please also send me the bug report code from that new project so I can take a closer look.

Thanks in advance!

[saswat216]

Hi Juansarmi,
​Thanks for taking a look at this.
​To answer your questions regarding the environment (which were included at the bottom of the original report):
​FlutterFlow version: 6.6.9
​Platforms tested: Android & iOS
​Operating Systems / Devices: Android 15 (Physical Device) and iOS Simulator (iPhone 17), flutterflow desktop app in both Mac Os 26.3 and windows 11 pc. (Both producing same issue)

​Regarding the blank project:
Because this bug forces the entire navigation stack and complex page layouts to rebuild upon viewInsets changes, the SurfaceFrame::Submit delays are naturally much harder to observe on a completely empty page. The jank becomes a release-blocking issue once the widget tree has standard production weight.
​For this reason, I have already granted explicit permission for the FlutterFlow team to access and test my actual project. Could you please access my project directly to reproduce this? You can use the links provided in the "Steps to Reproduce" section of my original post (e.g., the Add Fuel Log or Add Service Log pages).

Testing it directly in our environment is the fastest way to see the massive rebuild cycle and UI jank we are experiencing.
​Let me know what you find when profiling those pages, or if we can jump on a quick call to look at the DevTools timeline together.

[saswat216]

@Juansarmi can you update status please. All the information are given. Dont delay this issue.t

[saswat216]

Please update