Bug 16795 - Custom UI is not instantiating
Summary: Custom UI is not instantiating
Status: RESOLVED DUPLICATE of bug 16377
Alias: None
Product: Android
Classification: Xamarin
Component: Mono runtime / AOT Compiler ()
Version: 4.8.x
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: ---
Assignee: Jonathan Pryor
Depends on:
Reported: 2013-12-13 22:31 UTC by Paul Johnson
Modified: 2013-12-17 12:51 UTC (History)
1 user (show)

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 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:

Description Paul Johnson 2013-12-13 22:31:34 UTC
As described at http://forums.xamarin.com/discussion/comment/37957#Comment_37957, I have created a custom spinner which should be instantiated when called from a reference in the design axml file.

The code crashing as the instance has not been created (or has been garbage collected way too early - not sure which).

using Xam.Android 4.10.2 (alpha) on a Mac Mini (OSX.9)
Comment 1 Jonathan Pryor 2013-12-16 15:11:17 UTC
This is probably a dupe of Bug #16377.

*** This bug has been marked as a duplicate of bug 16377 ***
Comment 2 Paul Johnson 2013-12-16 17:33:58 UTC
Urgh - I can't access #16377
Comment 3 Jonathan Pryor 2013-12-17 12:51:31 UTC
The bug is that the .ctor(IntPtr, JniHandleOwnership) is invoked, but _not_ the e.g. View(Context) constructor, which causes all manner of breakage.

This has since been fixed, and will be present in the 4.11/4.12 series. Luck willing, we'll have a beta out before the end of the year...