Alex Fernandez
Alex Fernandez
KeyBoard is not opening for TextFormField in some iOS devices after adding flutter-unity-view-widget
We are seeing this in our project as well. @juicycleff Any suggestions? After we use a webview to authenticate with Google or Facebook it starts working again. This only happens...
KeyBoard is not opening for TextFormField in some iOS devices after adding flutter-unity-view-widget
Thanks for the reply @juicycleff. Here is what I am seeing. iPhone 6s, iOS 12.1 https://user-images.githubusercontent.com/825344/168464187-12134fbb-e22f-4067-8c0b-d2440ceb4890.MP4 iPhone 13, iOS 15.4.1 https://user-images.githubusercontent.com/825344/168464218-42640621-3cf9-4805-a526-28eb4e20b70b.MP4 As you can see, the keyboard does not open...
KeyBoard is not opening for TextFormField in some iOS devices after adding flutter-unity-view-widget
@juicycleff I can not re-open this ticket since I am not the author.
If you add `guardNonMatching: true,` to the current `BeamGuard` on line 225 this also happens. Looks to be something related to that.
Thank you for that suggestion. I was thinking about a `try {} catch {}` as well but didn't know what implications it may have. We will use that for now!
Seeing this as well. 
+1 for Flutter. I'd love the details for how to create the plugin if Figma has no plans to support it.
Looks like [this specifically](https://github.com/SebastienBtr/Dash-Chat-2/blob/main/lib/src/widgets/message_row/default_message_text.dart#L106-L116) is stopping the text size from being controlled via the [textTheme](https://api.flutter.dev/flutter/material/TextTheme-class.html). For the short term (and easy solution) you could mark all of your messages as...
The biggest offender here is that `ParsedText` needs to consume the theme data. ``` ParsedText( parse: messageOptions.parsePatterns != null ? messageOptions.parsePatterns! : defaultParsePatterns, text: text, style: TextStyle( color: isOwnMessage ?...
> Did you try something like that: > > ``` > style: Theme.of(context).textTheme.bodySmall.copyWith( > color: isOwnMessage > ? messageOptions.currentUserTextColor(context) > : messageOptions.textColor, > ) > ``` > > Not sure...