tree 2e19b17aaf1225ae775bdc231b36299aba86616d
parent f15b259fe98cc83f5ccbbb425be1b89178f4475c
author hellohuanlin <41930132+hellohuanlin@users.noreply.github.com> 1699991886 -0800
committer GitHub <noreply@github.com> 1699991886 +0000
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJlU9FOCRBK7hj4Ov3rIwAAxX8IAKamRLwygQ2vAMUapghtSlrJ
 Xetii0D+bXIUE42gwgwFtUfur+c1bbbnXFsJpMzznMHsri9kCS8vIUx/mY3Y4Mk8
 pdI4zDIZcog/B/JAIk9V65duRTCIBsyAk2s7S6yeNO+vOL29cOabM14L5Mhzp6tF
 2VXeVvS43Vj+IPE7ZBUqVHBeewwsnU1KOb2ssmoZot7uMORX8vTtOTgrOx6Y0rPS
 F7ojxSX0+2OyPnzuq7mVh0mElJTdpA1HkHBAb7iPCAKI7T1kOcwj7MX0b4lpjYur
 NGMG/8S+CAVM64QPGx5fmxi/zaaRJDcptyOUbVYsmEF3U27j9TqnN2gheGFCcrA=
 =AcqD
 -----END PGP SIGNATURE-----
 

[ios17][text_input]fix ios 17.0 keyboard freeze when switching languages (without relying on text affinity) (#47566)

After close examination of the UIKit's default string tokenizer, when querying the line enclosing the end of doc position **in forward direction**, we should return nil (regardless whether the position is forward or backward affinity). 

This aligns with the [API doc](https://developer.apple.com/documentation/uikit/uitextinputtokenizer/1614464-rangeenclosingposition?language=objc): 

> If the text position is at a text-unit boundary, it is considered enclosed only if the next position in the given direction is entirely enclosed.

Will cherry pick this soon. Otherwise it will be less and less important as users upgrade to iOS 17.1. 

### Why my previous workaround also works? 

It turns out my previous workaround PR https://github.com/flutter/engine/pull/46591 works only because our misuse of text affinity in our text input. Specifically, when adding text affinity support, we only added it to `FlutterTextPosition`, but not `FlutterTextRange`. So when getting the beginning/end position from the range, we assign arbitrary affinities. 

*List which issues are fixed by this PR. You must list at least one issue.*

https://github.com/flutter/engine/pull/46591

*If you had to change anything in the [flutter/tests] repo, include a link to the migration guide as per the [breaking change policy].*

[C++, Objective-C, Java style guides]: https://github.com/flutter/engine/blob/main/CONTRIBUTING.md#style