Bug 37712 - Binding throws Null Pointer Exception when Updating Tab Page Title..
Summary: Binding throws Null Pointer Exception when Updating Tab Page Title..
Status: RESOLVED DUPLICATE of bug 27350
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 1.5.1
Hardware: Other Linux
: Normal major
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2016-01-15 03:38 UTC by soumya
Modified: 2016-02-11 19:24 UTC (History)
9 users (show)

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

Source code (51.81 KB, application/x-zip-compressed)
2016-01-15 03:47 UTC, soumya

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 soumya 2016-01-15 03:38:25 UTC
Binding throws Null Pointer Exception when Updating Tab Page Title..

UI Carsh in Tab title update in OnAppearing() when Navigated back from another page. Please find attached source code to reproduce issue..
Comment 1 soumya 2016-01-15 03:47:36 UTC
Created attachment 14592 [details]
Source code
Comment 2 Stephane Delcroix 2016-01-15 11:01:24 UTC
I can confirm this. it only happens on "legacy" android activity, but not on AppCompat
Comment 3 soumya 2016-01-18 21:55:04 UTC
Thankyou Stephane for the confirmation. My targeted API is 16~19 (for now) and due to that moving to AppCompat is less likely.. I am looking forward to hear from you any workaround/ fixes for this issue..

Comment 4 Paul Diston 2016-02-08 10:27:42 UTC
I have experienced this issue for nearly a year and I am still waiting for a resolution, please see bug 27350
Comment 5 Paul DiPietro [MSFT] 2016-02-11 19:24:45 UTC

*** This bug has been marked as a duplicate of bug 27350 ***