SfTextInputLayout not properly auto-sizing with editor in iOS

[Alex]

I am using Xamarin.Forms with 17.3.0.28 and have an SfTextInputLayout containing an Editor. These controls are within a Grid row that is set to "auto" height. I have the Editor set to AutoSize when the text changes.

When someone types a long message, the text will wrap to the next line and the Editor's height increasing. When they erase text, the height changes as well. This all works well.

The problem comes with other code sets the Editor's text value to a long string.
Lets say I said:
txtMsg.Text = "Hello this is a long message that will wrap to another line and make the editor height grow."

Then I tap the Editor and try to erase some of the text area. It is as if the Editor itself shrinks in height, but the SfTextInputLayout does not. This results in the SfTextinputLayout's borders and whatnot cascading off the screen and the "Hint" becomes displaced. I have attached a couple screenshots of this.

Attachment: screenshotsOfIssue_ad2025fa.zip

[Rachel A]

Hi Alex, 

  

We were able to reproduce the issue at our end. We have confirmed this as an issue and logged bug report. We will include the fix in our Volume 4 release which will be available by the mid-December 2019. You can track the bug status from the below link. 

  

Feedback: https://www.syncfusion.com/feedback/10313/sftextinputlayout-control-size-doesnt-change-when-setting-multi-text-line-in-the 

  

If you have any more specification/precise replication procedure or a scenario to be tested, you can add it as a comment in the portal link above. We appreciate your patience until then. 

 

Note: The provided feedback link is private, and you need to login to view this feedback. 

 

Thanks, 

Rachel. 

[Alex]

Is there any temporary workaround for this issue so I can publish my app?

I should note I only see this issue on iOS and not Android. I am not currently targeting UWP at all.

[Lakshmi Radha Krishnan]

Hi Alex,

Sorry for the delay.

We are not able to provide workaround for this issue. We will provide patch for this issue on or before November 29th, 2019. We appreciate your patience until then.

Regards,

Lakshmi R.

[Alex]

Hi Alex,

Sorry for the delay.

We are not able to provide workaround for this issue. We will provide patch for this issue on or before November 29th, 2019. We appreciate your patience until then.

Regards,

Lakshmi R.

Hey, sorry for being impatient, but I noticed there was a weekly release today (11/26) and the bug was not patched in this release.

You mentioned a fix would be implemented on or before 11/29, does this mean a second release is going to happen this week?

[Lakshmi Radha Krishnan]

Hi Alex,

We have mentioned to provide patch for this issue and we have not included the fix in our last weekly release (17.3.0.29). As promised earlier, we will provide patch for this issue on  November 29, 2019.

Regards,

Lakshmi R.

[Lakshmi Radha Krishnan]

Hi Alex,

 

We have fixed the issue in iOS platform. Please find the patch details.

 

Please find the patch setup from the below location.    

http://syncfusion.com/Installs/support/patch/17.3.0.26/1168653/F149298/SyncfusionPatch_17.3.0.26_1168653_11292019090100092_F149298.exe

 

 (OR)  

   

Please find the patch assemblies from the below location.     

http://syncfusion.com/Installs/support/patch/17.3.0.26/1168653/F149298/SyncfusionPatch_17.3.0.26_1168653_11292019090100092_F149298.zip

 

(OR)  

   

Please find the NuGet from the below location.  

http://syncfusion.com/Installs/support/patch/17.3.0.26/1168653/F149298/SyncfusionNuget_17.3.0.26_1168653_11292019090100092_F149298.zip

 

Assembly Version: 17.3.0.26

   

Disclaimer:    

Please note that we have created this patch for version 17.3.0.26 specifically to resolve the issue in this incident. If you have received other patches for the same version for other products, please apply all patches in the order received.

 

Could you please crosscheck at your end by clearing the NuGet cache as mentioned in this link? and refer the provided NuGet and confirm us whether you can resolve this issue. We will include this fix in our Volume 4 beta release which is scheduled to be rolled out in the first week of December.

 

 

Regards,

Lakshmi R.