1. Home
  2. Forum
  3. Xamarin.Forms
  4. requestLayout() improperly called by SfTabView

requestLayout() improperly called by SfTabView

I'm using the SfTabView control in my projects. On Android I keep getting this logs:


[View] requestLayout() improperly called by crc64f72ebd847d591cfa.SfTabView{22703c9 V.E...... ........ 0,0-1036,886 #59} during second layout pass: posting in next frame

[View] requestLayout() improperly called by crc64f72ebd847d591cfa.ContentContainer{5cc9c7 VFE...... ........ 0,0-1036,886} during second layout pass: posting in next frame

[View] requestLayout() improperly called by crc64f72ebd847d591cfa.SfTabView{5aa68a4 VFE...... ......I. 0,0-1036,886 #82} during second layout pass: posting in next frame

[View] requestLayout() improperly called by crc64f72ebd847d591cfa.ContentContainer{55d8c46 VFE...... ......I. 0,0-1036,886} during second layout pass: posting in next frame

Is this a bug of the control itself?


Thanks for looking int


17 Replies 1 reply marked as answer
SS Suganya Sethuraman Syncfusion Team August 2, 2021 12:43 PM UTC

Hi Andreas,

Greetings from Syncfusion.

We are currently validating on this, and we will update the complete details on August 4, 2021. We appreciate your patience until then.

Regards,
Suganya Sethuraman. 


AR Andreas Reitberger replied to Suganya Sethuraman August 3, 2021 06:15 AM UTC

Thanks for your reply.

It seems to happen if I'm using two TabViews in one page, while one is set "IsVisible" false.


I have a Dashboard page with two MainViews, one optimized for tablets, one for phones.

Depending on the device, one of them is visible and the other is not.

Maybe this helps to identify the iusse.


JK Jeya Kasipandi Syncfusion Team August 4, 2021 01:15 PM UTC

Hi Andreas, 

Thanks for your patience.

We have validated your query and fixed the reported issue. Please find the custom assemblies from below link.


Assembly version :19.2.0.51

Since 19.2.0.51 is a weekly NuGet release, we are not able to generate patch in 19.2.0.51 version. We can generate patch only for Main release and SP1 release versions, so we have provided the custom assemblies in 19.2.0.51.

Disclaimer:
Please note that we have created custom assembly for version 19.2.0.51 specifically to resolve the issue reported in this . If you have received other patches for the same version for other products, please apply all patches in the order received.

Please refer the below link for how to apply custom assemblies.
  
Can you please check with the above and let us know the reported issue resolved or not? 

Regards,
Jeya K 


AR Andreas Reitberger replied to Jeya Kasipandi August 4, 2021 01:31 PM UTC

Hi,

thanks for the fix. Will this be added in a later update as well?

Do you have an ETA for this? 


Thank you,

Andreas


JK Jeya Kasipandi Syncfusion Team August 5, 2021 08:09 AM UTC

Hi Andreas,

Thanks for the update.

We will include the fix in our weekly nuget release which is expected to be rolled out on August 24 ,2021.We appreciate your patience until then.We will let you know once the weekly nuget is rolled out.

Regards,
Jeya K

AR Andreas Reitberger replied to Jeya Kasipandi August 5, 2021 08:09 AM UTC

Hi Jeya,

awesome, thank you :)


JK Jeya Kasipandi Syncfusion Team August 5, 2021 09:05 AM UTC

Hi Andreas,

Most welcome.

Regards,
Jeya K

AR Andreas Reitberger replied to Jeya Kasipandi August 24, 2021 11:40 AM UTC

Hi Jeya,

I updated to the latest version today. The issue is still in the package. Or wasn't this fixed in 19.2.0.57?

Thank you!


JK Jeya Kasipandi Syncfusion Team August 25, 2021 05:55 AM UTC

Hi Andreas,

Sorry for the inconvenience caused.

Due to some pending test cases to ensure the fix, we were unable to include the fix in weekly nuget version 19.2.0.57 and we will include the fix in our upcoming weekly nuget release which will be available on August 31,  2021.We appreciate your patience until then.

Regards,
Jeya K

AR Andreas Reitberger replied to Jeya Kasipandi August 25, 2021 03:36 PM UTC

Hi Jeya,

thanks for the update :) Then I'll wait for the next release.


JK Jeya Kasipandi Syncfusion Team August 26, 2021 06:08 AM UTC

Hi Andreas,

Thanks for the update. As we promised earlier, we will move the fix in our upcoming weekly nuget release which will be available on August 31, 2021.We appreciate your patience until then.

Regards,
Jeya K

JK Jeya Kasipandi Syncfusion Team August 31, 2021 11:52 AM UTC

Hi Andreas,

We deeply regret for inconvenience.

Due to some technical problem, we were unable to include the fix for the reported issue in today weekly release nuget. We will move the fix in our upcoming weekly NuGet which is expected to be rolled out on September 07, 2021.

We appreciate your patience until then.

Regards,
Jeya K

AR Andreas Reitberger replied to Jeya Kasipandi August 31, 2021 03:01 PM UTC

Hi Jeya,

thanks for letting me know. I'll wait then till the next update.

Best,

Andreas


JK Jeya Kasipandi Syncfusion Team September 1, 2021 12:10 PM UTC

Hi Andreas,

Thanks for the update. We will move the fix in our weekly nuget release which will be available on September 07, 2021.We will let you know once the weekly nuget is rolled out.We appreciate your patience until then.

Regards,
Jeya K

JK Jeya Kasipandi Syncfusion Team September 7, 2021 08:21 AM UTC

Hi Andreas,

Thanks for your patience.

We have included the fix in our latest Weekly NuGet release v19.2.0.60 which is available for download (https://www.nuget.org/ ). We thank you for your support and appreciate your patience in waiting for this update. Please get in touch with us if you would require any further assistance.

Regards,
Jeya K

Marked as answer
AR Andreas Reitberger September 7, 2021 04:23 PM UTC

Hi Jeya,

thank you. Just updated and it's working :) 


JK Jeya Kasipandi Syncfusion Team September 8, 2021 08:05 AM UTC

Hi Andreas,

Thanks for the update.

We are glad to know that the reported issue has been resolved. Please let us know if you have any other queris.

Regards,
Jeya K 


Loader.
Up arrow icon