Bug 39580 - Second layout and measure call was not called for view added inside thread
Summary: Second layout and measure call was not called for view added inside thread
Status: RESOLVED INVALID
Alias: None
Product: Android
Classification: Xamarin
Component: General ()
Version: 5.1
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Jonathan Pryor
URL:
Depends on:
Blocks:
 
Reported: 2016-03-14 09:09 UTC by Dharmendar
Modified: 2017-06-28 08:08 UTC (History)
3 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:


Attachments
Replication sample which contains the above mentioned case. (11.28 KB, application/zip)
2016-03-14 09:09 UTC, Dharmendar
Details


Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED INVALID

Description Dharmendar 2016-03-14 09:09:43 UTC
Created attachment 15395 [details]
Replication sample which contains the above mentioned case.

When child view is added to parent view inside the thread then the second layout and measure call was not called. But it is working fine for the child which added outside thread. Is there any reason behind this ?
Comment 1 Prashant [MSFT] 2017-06-28 08:08:05 UTC
Thank you for taking the time to submit this report. After reviewing the description of this bug, we believe it no longer affects the current version of Xamarin.Android. If you are still experiencing the issue after updating your packages, please reopen this report with an attached reproduction.