Bug 43492 - AbsoluteLayout rendering
Summary: AbsoluteLayout rendering
Status: CONFIRMED
Alias: None
Product: Forms
Classification: Xamarin
Component: iOS ()
Version: unspecified
Hardware: Macintosh Mac OS
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2016-08-17 21:01 UTC by Andrew
Modified: 2016-10-22 12:15 UTC (History)
4 users (show)

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

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 for Bug 43492 on Developer Community or GitHub if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: Developer Community HTML or GitHub Markdown
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:
Status:
CONFIRMED

Description Andrew 2016-08-17 21:01:08 UTC
# Steps to reproduce

run solution.  Xamarin Forms iOS only.

NotWorkingPage.cs listview does not scroll
WorkingPage.cs listview scrolls

the difference is when I set the layout.  If set before I assign Content, works. If the content is set, then I update the content in the propertychanged method, the page is not re-created?

			// Android OK.
			// iOS failed

			//MainPage = new NavigationPage(new WorkingPage());

			MainPage = new NavigationPage(new NotWorkingPage());

https://drive.google.com/file/d/0B42pzCe_yNDoSXkwbWw5TUNIcWM/view?usp=sharing

# Expected behavior

Both work on Xamarin Forms iOS

NotWorkingPage.cs 
WorkingPage.cs

# Actual behavior

NotWorkingPage.cs  works

# Supplemental info (logs, images, videos)

https://drive.google.com/file/d/0B42pzCe_yNDoSXkwbWw5TUNIcWM/view?usp=sharing

# Test environment (full version information)
			  
=== Xamarin Studio Enterprise ===

Version 6.0.2 (build 73)
Installation UUID: c6cc2bf2-3d75-4e51-bb1f-b12a2a84f591
Runtime:
	Mono 4.4.2 (mono-4.4.0-branch-c7sr1/f72fe45) (64-bit)
	GTK+ 2.24.23 (Raleigh theme)

	Package version: 404020011

=== Xamarin.Profiler ===

Not Installed

=== Apple Developer Tools ===

Xcode 7.3.1 (10188.1)
Build 7D1014

=== Xamarin.iOS ===

Version: 9.8.2.22 (Visual Studio Enterprise)
Hash: f37444a
Branch: cycle7-sr1
Build date: 2016-07-28 12:17:02-0400

=== Xamarin.Android ===

Version: 6.1.2.21 (Visual Studio Enterprise)
Android SDK: /Users/mccorma/Library/Developer/Xamarin/android-sdk-macosx
	Supported Android versions:
		4.0.3  (API level 15)
		4.1    (API level 16)
		4.2    (API level 17)
		4.3    (API level 18)
		4.4    (API level 19)
		4.4.87 (API level 20)
		5.0    (API level 21)
		5.1    (API level 22)
		6.0    (API level 23)

SDK Tools Version: 25.2.2
SDK Platform Tools Version: 24.0.1
SDK Build Tools Version: 23.0.3

Java SDK: /usr
java version "1.8.0_91"
Java(TM) SE Runtime Environment (build 1.8.0_91-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.91-b14, mixed mode)

Android Designer EPL code available here:
https://github.com/xamarin/AndroidDesigner.EPL

=== Xamarin Android Player ===

Version: 0.6.5
Location: /Applications/Xamarin Android Player.app

=== Xamarin.Mac ===

Version: 2.8.2.22 (Visual Studio Enterprise)

=== Xamarin Inspector ===

Version: 0.9.0.14
Hash: 4d868da
Branch: master
Build date: Mon Jun 13 19:14:13 UTC 2016

=== Build Information ===

Release ID: 600020073
Git revision: a6f7a24a9723a2d4f5d33c176615b0d44703ab5b
Build date: 2016-07-26 13:36:15-04
Xamarin addins: f5acb37866a0141bc5ddbe95118f18dae4014568
Build lane: monodevelop-lion-cycle7-sr1

=== Operating System ===

Mac OS X 10.11.6
Darwin ITM-mccorma-f8j8.local 15.6.0 Darwin Kernel Version 15.6.0
    Thu Jun 23 18:25:34 PDT 2016
    root:xnu-3248.60.10~1/RELEASE_X86_64 x86_64

=== Enabled user installed addins ===

Xamarin Inspector 0.9.0.14
Comment 1 adrianknight89 2016-10-22 04:35:52 UTC
This also happens if you try to do "this.Content = CreateLoadingIndicator(this.Content);" in OnAppearing

As a workaround, you could do:

var c = Content;
Content = null;
Content = CreateLoadingIndicator(c);

The trick is passing another reference instead of the reference for Control and reassigning it on return.
Comment 2 Andrew 2016-10-22 12:15:51 UTC
Should it work in onappearing? It is a minor bug if it is a bug. I do not use the onappearing in this bug but did when i was testing it. Can mark this low priority.