Bug 41601 - OnAppearing not being called when navigating from a tabbed Page
Summary: OnAppearing not being called when navigating from a tabbed Page
Status: RESOLVED FIXED
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms ()
Version: 2.3.0
Hardware: PC All
: --- normal
Target Milestone: 2.0.0
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2016-06-08 15:14 UTC by gandharvkumargarg
Modified: 2016-08-11 10:51 UTC (History)
2 users (show)

Tags:
Is this bug a regression?: No
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:
Status:
RESOLVED FIXED

Description gandharvkumargarg 2016-06-08 15:14:14 UTC
In a tabbed page when we navigate to a new content page and when pop from the new content page and come back to the tabbed page neither the OnAppearing() nor the Constructor is called . hence unable to update the data.   Happens only in android. In iOS the OnAppearing() function is being called. and we can update the data 

P.S.- as a workaround we have used messaging center for the android inspired from the xamarin evolve application .
Comment 1 Rui Marinho 2016-08-11 10:51:33 UTC
Thank you for taking the time to submit this report. After reviewing the description of this bug, we believe it no longer 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

Warm regards,
Xamarin Forms Team