Skip to content
This repository has been archived by the owner on May 1, 2024. It is now read-only.

[WPF] Additional OnAppearing when using Navigation.PushAsync #3726

Closed
MartinWegner opened this issue Sep 6, 2018 · 3 comments · Fixed by #3372
Closed

[WPF] Additional OnAppearing when using Navigation.PushAsync #3726

MartinWegner opened this issue Sep 6, 2018 · 3 comments · Fixed by #3372

Comments

@MartinWegner
Copy link

Description

Switching between Contentpages with Navigation.PushAsync causes an additional set of functioncalls to OnAppearing and OnDisappearing. The back Button has the same issue. This seems to be specific to WPF.

Steps to Reproduce

  1. Download ReproCase
  2. Start app and click "Nav" Button
  3. Watch the console output window

Expected Behavior

BoxViewClock.MainPage Void OnDisappearing()
BoxViewClock.Page1 Void OnAppearing()

Actual Behavior

BoxViewClock.MainPage Void OnDisappearing()
BoxViewClock.MainPage Void OnAppearing()
BoxViewClock.Page1 Void OnAppearing()
BoxViewClock.MainPage Void OnDisappearing()

Basic Information

  • Version with issue: 3.2.0.729530-pre2 + 3.1.0.697729 (Latest stable and Latest prerelease)
  • Last known good version: none
  • IDE: Microsoft Visual Studio Enterprise 2017 Version 15.8.0
  • Platform Target Frameworks:
    • WPF: 4.7
  • Nuget Packages:
    NETStandard.Library {2.0.3} BoxViewClock
    Xamarin.Forms {3.2.0.729530-pre2} BoxViewClock
    OpenTK {3.0.1} BoxViewClock.WPF
    OpenTK.GLControl {3.0.1} BoxViewClock.WPF
    WpfLightToolkit {1.0.3} BoxViewClock.WPF
    Xamarin.Forms {3.2.0.729530-pre2} BoxViewClock.WPF
    Xamarin.Forms.Platform.WPF {3.2.0.729530-pre2} BoxViewClock.WPF

Reproduction Link

ReproCase_DoubleOnAppearing.zip

@pauldipietro pauldipietro added this to New in Triage Sep 6, 2018
@pauldipietro
Copy link
Contributor

Thank you for the reproduction which displays the behavior.

@pauldipietro pauldipietro moved this from New to Ready For Work in Triage Sep 6, 2018
@mohachouch
Copy link
Contributor

mohachouch commented Sep 27, 2018

I tried with the version 3.3.0.840541-pre1 the bug no longer appears.

Could you try with your solution? @MartinWegner Thanks

@mohachouch
Copy link
Contributor

@samhouts Bug not reproduced on the latest version. I think the PR # 3372 to fix this bug.

@samhouts samhouts closed this as completed Oct 5, 2018
Triage automation moved this from Ready For Work to Closed Oct 5, 2018
@samhouts samhouts added this to In Progress in v3.4.0 Oct 5, 2018
@samhouts samhouts moved this from In Progress to Done in v3.4.0 Oct 8, 2018
@samhouts samhouts removed this from Closed in Triage Oct 8, 2018
@samhouts samhouts removed this from Done in v3.4.0 Nov 19, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants