Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
I created a custom renderer to display a MediaElement on a second page I pushed using PushAsync() using NavigationPage. This works wonderfully. The problem is when I try to use the back button to go back to my first page, the custom renderer for the media element complains at the "SetNativeControl(new MediaElement())" line.
protected override async void OnElementChanged(ElementChangedEventArgs<MyRenderer> e)
if (Control == null)
An exception of type 'System.NullReferenceException' occurred in Xamarin.Forms.Platform.WinRT.DLL but was not handled in user code
at Xamarin.Forms.Platform.WinRT.VisualElementRenderer`2.SetNativeControl(TNativeElement control)
Microsoft Visual Studio Professional 2015
Version 14.0.23107.0 D14REL
Microsoft .NET Framework
Installed Version: Professional
Visual Basic 2015 00322-50050-46449-AA877
Microsoft Visual Basic 2015
Visual C# 2015 00322-50050-46449-AA877
Microsoft Visual C# 2015
Windows Phone SDK 8.0 - ENU 00322-50050-46449-AA877
Windows Phone SDK 8.0 - ENU
Visual Studio Tools for Universal Windows Apps 14.0.23309.00 d14oob
The Visual Studio Tools for Universal Windows apps allow you to build a single universal app experience that can reach every device running Windows 10: phone, tablet, PC, and more. It includes the Microsoft Windows 10 Software Development Kit.
Xamarin 184.108.40.2067 (1390b70)
Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android.
Xamarin.Android 220.127.116.11 (d300845)
Visual Studio plugin to enable development for Xamarin.Android.
Xamarin.iOS 18.104.22.168 (ea30b32)
Visual Studio extension to enable development for Xamarin.iOS.
This issue should be closed. Issue has already been reported:
(In reply to Adam from comment #1)
> This issue should be closed. Issue has already been reported:
I'm not sure that your issue is a duplicate; bug 21457 is an iOS issue and your issue seems to be on Windows. Can you attach a small project which reproduces the error you're seeing?
Thank you for taking the time to submit this report. After reviewing the description of this bug, we no longer believe it affects the current version of Xamarin.Forms. If you are still experiencing the issue after updating your packages, please reopen this report with an attached reproduction.
For your convenience, we have created some reproduction best practices viewable here: https://gist.github.com/jassmith/92405c300e54a01dcc6d
Xamarin Forms Team
Created attachment 15421 [details]