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.
There's a bug in private method Android.Views.View.IOnFocusChangeListener.OnFocusChange(Android.Views.View v, bool hasFocus)
I have noticed that in the for loop the variable parent can be null at times causing a NullReferenceException.
for (Element parent = this.Element.Parent; !(parent is Page); parent = parent.Parent)
Only adding a null check would fix it I think:
for (Element parent = this.Element.Parent; parent != null && !(parent is Page); parent = parent.Parent)
Thank you for taking the time to submit the bug. We tried to reproduce the issue you reported but were unable given the description. If you could please attach a reproduction to the bug by starting with a clean Xamarin.Forms project and adding just the code necessary to demonstrate the issue we would very much appreciate it.
Xamarin Forms Team
I confirm this. This little sample fails:
public class App : Application
var page = new ContentPage();
var entry = new Entry();
page.Content = entry;
page.Appearing += (sender, args) =>
page.Content = null;
this.MainPage = page;
Created attachment 11540 [details]
See sergeys commenta and repro
Should be fixed in 1.4.3 final.
I have checked this issue with Xamarin.Forms.184.108.40.20664-pre3 and I am not getting any exception.
Hence closing this issue.