fix#180842

The issue was caused by#173598.

When there is a single TextField, the MethodChannel calls are as follows:

handleMethodCall: TextInput.setClienthandleMethodCall: TextInput.setEditableSizeAndTransformhandleMethodCall: TextInput.setMarkedTextRecthandleMethodCall: TextInput.setCaretRecthandleMethodCall: TextInput.setStylehandleMethodCall: TextInput.setEditingStatehandleMethodCall: TextInput.showhandleMethodCall: TextInput.requestAutofillhandleMethodCall: TextInput.clearClienthandleMethodCall: TextInput.hide

However, when there are two TextFields, the calls become:

handleMethodCall: TextInput.setClienthandleMethodCall: TextInput.setEditableSizeAndTransformhandleMethodCall: TextInput.setMarkedTextRecthandleMethodCall: TextInput.setCaretRecthandleMethodCall: TextInput.setStylehandleMethodCall: TextInput.setEditingStatehandleMethodCall: TextInput.showhandleMethodCall: TextInput.requestAutofillhandleMethodCall: TextInput.clearClienthandleMethodCall: TextInput.setClienthandleMethodCall: TextInput.setEditableSizeAndTransformhandleMethodCall: TextInput.setMarkedTextRecthandleMethodCall: TextInput.setCaretRecthandleMethodCall: TextInput.setStylehandleMethodCall: TextInput.setEditingStatehandleMethodCall: TextInput.showhandleMethodCall: TextInput.requestAutofillhandleMethodCall: TextInput.clearClienthandleMethodCall: TextInput.hide

In the multi-field case,clearTextInputClient is called beforesetTextInputClient for the next field. CallingremoveFromSuperview duringclearTextInputClient causes the keyboard to briefly dismiss and reappear (flicker).

This PR defers theremoveFromSuperview call fromclearTextInputClient tohideTextInput, using a pending flag (_pendingInputViewRemoval). The input view is removed only afterresignFirstResponder dismisses the keyboard.showTextInput resets the flag to prevent stale flags from causing unintended removal when switching fields.

For autofill contexts, a separate flag (_pendingAutofillRemoval) defers removal totriggerAutofillSave, preserving the existing autofill save behavior.

Pre-launch Checklist

• I read theContributor Guide and followed the process outlined there for submitting PRs.
• I read theTree Hygiene wiki page, which explains my responsibilities.
• I read and followed theFlutter Style Guide, includingFeatures we expect every widget to implement.
• I signed theCLA.
• I listed at least one issue that this PR fixes in the description above.
• I updated/added relevant documentation (doc comments with///).
• I added new tests to check the change I am making, or this PR istest-exempt.
• I followed thebreaking change policy and addedData Driven Fixes where supported.
• All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel onDiscord.

Note: The Flutter team is currently trialing the use ofGemini Code Assist for GitHub. Comments from thegemini-code-assist bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.