- Home
- Forum
- Xamarin.Forms
- SfTextInputLayout stopped working on iOS after updating to the latest version
SfTextInputLayout stopped working on iOS after updating to the latest version
Hi,
I recognized that all my SfTextInputLayouts stopped working in my iOS app when I updated to the latest version.
I'm using following Xamarin.Forms version 5.0.0.1829-pre6
I also get this debug messages if I try to click into a control which is enclosed from a TextInputLayout in Visual Studio.
2020-12-30 06:23:24.981232+0100 MYAPPNAME.iOS[23314:299367] [LayoutConstraints] Unable to simultaneously satisfy constraints.
Probably at least one of the constraints in the following list is one you don't want.
Try this:
(1) look at each constraint and try to figure out which you don't expect;
(2) find the code that added the unwanted constraint or constraints and fix it.
(
"<NSLayoutConstraint:0x6000035925d0 'accessoryView.bottom' _UIRemoteKeyboardPlaceholderView:0x7fd688d04280.bottom == _UIKBCompatInputView:0x7fd68b1425a0.top (active)>",
"<NSLayoutConstraint:0x600003584c30 'assistantHeight' TUISystemInputAssistantView:0x7fd68b107430.height == 44 (active)>",
"<NSLayoutConstraint:0x60000359c050 'assistantView.bottom' TUISystemInputAssistantView:0x7fd68b107430.bottom == _UIKBCompatInputView:0x7fd68b1425a0.top (active)>",
"<NSLayoutConstraint:0x600003592490 'assistantView.top' V:[_UIRemoteKeyboardPlaceholderView:0x7fd688d04280]-(0)-[TUISystemInputAssistantView:0x7fd6
8b107430] (active)>"
)
Will attempt to recover by breaking constraint
<NSLayoutConstraint:0x600003592490 'assistantView.top' V:[_UIRemoteKeyboardPlaceholderView:0x7fd688d04280]-(0)-[TUISystemInputAssistantView:0x7fd68b107430] (active)>
Make a symbolic breakpoint at UIViewAlertForUnsatisfiableConstraints to catch this in the debugger.
The methods in the UIConstraintBasedLayoutDebugging category on UIView listed in <UIKitCore/UIView.h> may also be helpful.
2020-12-30 06:23:25.037963+0100 MYAPPNAME.iOS[23314:299367] [Snapshotting] Snapshotting a view (0x7fd68b1b6e80, _UIReplicantView) that has not been rendered at least once requires afterScreenUpdates:YES.
The iOS Simulator runs the latest iOS version as well.
Thank you for helping out,
Andreas
SIGN IN To post a reply.
4 Replies
1 reply marked as answer
SS
Sridevi Sivakumar
Syncfusion Team
December 31, 2020 10:15 AM UTC
Hi Andreas Reitberger,
Greetings from Syncfusion.
We would like to let you know that the reported problem is related to the framework level issue with XF 5.0 and we have already logged bug query in GitHub.
Link: https://github.com/xamarin/Xamarin.Forms/issues/12484
We will let you know once we got a generic solution to resolve this problem.
Regards,
Sridevi S.
Greetings from Syncfusion.
We would like to let you know that the reported problem is related to the framework level issue with XF 5.0 and we have already logged bug query in GitHub.
Link: https://github.com/xamarin/Xamarin.Forms/issues/12484
We will let you know once we got a generic solution to resolve this problem.
Regards,
Sridevi S.
AR
Andreas Reitberger
December 31, 2020 11:12 AM UTC
Thanks for letting me know that the issue is realted to XF5.x
Hopefully they will fix it soon.
Wish you a happy new years eve.
Stay safe,
Andreas
SS
Sridevi Sivakumar
Syncfusion Team
January 4, 2021 07:02 AM UTC
Hi Andreas Reitberger,
Thanks for your update. Once it is solved, we will let you know.
Please let us know if you need any further assistance.
Regards,
Sridevi S.
Thanks for your update. Once it is solved, we will let you know.
Please let us know if you need any further assistance.
Regards,
Sridevi S.
SS
Sridevi Sivakumar
Syncfusion Team
January 7, 2021 12:10 PM UTC
Hi Andreas Reitberger,
Thanks for your patience.
We glad to inform you that reported problem in Xamarin.Forms 5.0 pre-release version resolved in Xamarin.Forms 5.0.0.1874 Version.
So, please upgrade the Xamarin.Forms 5.0 stable version in your application to resolve this problem.
Please let us know if you have any other queries.
Regards,
Sridevi S.
Thanks for your patience.
We glad to inform you that reported problem in Xamarin.Forms 5.0 pre-release version resolved in Xamarin.Forms 5.0.0.1874 Version.
So, please upgrade the Xamarin.Forms 5.0 stable version in your application to resolve this problem.
Please let us know if you have any other queries.
Regards,
Sridevi S.
Marked as answer
SIGN IN To post a reply.
- 4 Replies
- 2 Participants
- Marked answer
-
AR Andreas Reitberger
- Dec 30, 2020 06:10 AM UTC
- Jan 7, 2021 12:10 PM UTC