This is Xamarin's bug tracking system. For product support, please use the support links listed in your Xamarin Account.
Bug 48517 - OnAppearing strange behavior when my application is resumed by Android OS
Summary: OnAppearing strange behavior when my application is resumed by Android OS
Status: RESOLVED DUPLICATE of bug 41322
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms (show other bugs)
Version: 2.3.3
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2016-12-01 12:30 UTC by Dmitry
Modified: 2016-12-01 19:33 UTC (History)
3 users (show)

See Also:
Tags:
Is this bug a regression?: ---
Last known good build:


Attachments

Description Dmitry 2016-12-01 12:30:59 UTC
I've got a strange behavior when application is resumed by Android OS, it could be a bug or some Forms' feature.

I'm using 2.3.3 XF with Android 15 SDK.

This is my navigation stack:

= First page
== Second page
=== Third page
==== Fourth page

All these pages have their OnAppearing overridden.

I switch pages with Navigation.PushAsync.

I'm on Fourth page and my application becomes hidden (OnPause method in Droid's MainActivity is calling), but when I return to my application (OnResume method in Droid's MainActivity is calling) the following happens:

1. First page's OnAppearing is being called.
2. Second page's OnAppearing is being called.
3. Third page's OnAppearing is being called.
4. Fourth page's OnAppearing is being called.

All these pages get their OnAppearing called, the same time I'm on the Fourth page and assume only its OnAppearing should be called. Then I go back (with pressing Back button) to the Third page and its OnAppearing is not being called.

This happens only when my application is resumed by Android OS, otherwise OnAppearing at every page calls fine.

Is it OK? Can anyone explain this?
Comment 1 adrianknight89 2016-12-01 15:25:58 UTC
I believe this was fixed in 2.3.4-pre1.
Comment 2 Samantha Houts 2016-12-01 19:33:41 UTC

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

Note You need to log in before you can comment on or make changes to this bug.