Created attachment 16109 [details]
XF2.2 solution with android project
This bug came in XF 2.2 and only happens when using FormsAppCompatActivity.
What happens in that all pages that are alive call onappearing/disappearing when you toggle outside app OR change activity when taking photos with Xam.Plugin.Media for example. The appearing calls trigger even after removing a Page from navigation stack with Navigation.RemovePage(), this is also shown in my repro. The bug is both on emulators and harware pre and post lollipop. If you use the standard FormsApplicationActivity everything works just like its supposed to. I´ve added a repro that perfectly shows you this. This forced me to dowgrade many of my projects since logic in appearing/disappearing events went totally crazy resulting in breaking my apps. Ive also tested the latest prerelease of XF2.3 and its the same thing there. Because this causes all pages in stack to call appearing when going back to app, the acutal appearing is not called when its actually appearing, same thing for disappearing.
Please fix this!
## Version information
Microsoft Visual Studio Professional 2015
Version 14.0.25123.00 Update 2
Microsoft .NET Framework
Installed Version: Professional
Visual Basic 2015 00322-40000-00000-AA983
Microsoft Visual Basic 2015
Visual C# 2015 00322-40000-00000-AA983
Microsoft Visual C# 2015
Visual C++ 2015 00322-40000-00000-AA983
Microsoft Visual C++ 2015
ASP.NET and Web Tools 2015.1 (Beta8) 14.1.11106.0
ASP.NET and Web Tools 2015.1 (Beta8)
Common Azure Tools 1.7
Provides common services for use by Azure Mobile Services and Microsoft Azure Tools.
A Visual Studio Extension that brings the GitHub Flow into Visual Studio.
GorillaPlayerPackage Extension 1.0
GorillaPlayerPackage Visual Studio Extension Detailed Info
Microsoft Azure Mobile Services Tools 1.4
Microsoft Azure Mobile Services Tools
NuGet Package Manager 3.4.0
NuGet Package Manager in Visual Studio. For more information about NuGet, visit http://docs.nuget.org/.
PreEmptive Analytics Visualizer 1.2
Microsoft Visual Studio extension to visualize aggregated summaries from the PreEmptive Analytics product.
SQL Server Data Tools 14.0.60311.1
Microsoft SQL Server Data Tools
TypeScript tools for Visual Studio
Workflow Manager Tools 1.0 1.0
This package contains the necessary Visual Studio integration components for Workflow Manager.
Xamarin 188.8.131.52 (0dd817c)
Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android.
Xamarin.Android 184.108.40.206 (a94a03b)
Visual Studio plugin to enable development for Xamarin.Android.
Xamarin.iOS 220.127.116.11 (3a25bf1)
Visual Studio extension to enable development for Xamarin.iOS.
##Steps to reproduce:
1. Download attachment
2. An alert will display triggered from OnAppearing, press ok
3.Navigate to page 2
4. Navigate to page 3
5. Toggle in and out of app, see output and dismiss Alerts.
(There are instructions in the app also)
The expected behaviour would be that the page calls appearing or disappearing when it actually is appearing or disappearing. It works just like its supposed to with standard FormsApplicationActivity instead of FormsAppCompatActivity
All pages that are alive AND removed from stack with Navigation.RemovePage() call Appearing/disappearing when toggling in and out of app, or taking photo (changing activity)
Any update on this? It's causing us quite a few problems as we launch the camera frequently and rely on the onAppearing once the camera has been dismissed.
Nothing has been done to solve it (based on what Xamarin has released)...
I've also filed a bug that's different to reproduce, but exposes the same observed behaviour - All pages in the navigation page firing OnAppearing event.
However, for the reported bug, it occurs for both FormsAppCompatActivity & FormsApplicationActivity.
I have this issue when I hit the power button to lock the screen. When I unlock, onappearing of previous pages will be called. :(
Created attachment 17407 [details]
Navigate to Page2 and then lock the screen. When you unlock, keyboard from Page1 will show.
I submitted a PR in case it fixes your use cases. Please see https://github.com/xamarin/Xamarin.Forms/pull/342
I tested the dlls from made from the PR on my repro. And it works like its supposed to! :D
Please Xamarin include this fix asap :)
Should be fixed in 2.3.4-pre1. Thank you!
GREAT! Thank you! :D
I have checked this issue with Xamarin.Forms 2.3.4-pre1 and I have used sample attached in comment #7 and followed instruction and observed that this issue has been fixed.
Hence closing this issue.
*** Bug 48517 has been marked as a duplicate of this bug. ***
Checked the issue with Xamarin.Forms 18.104.22.168-pre1, still getting reproduced. Please reopen the bug
## Preliminary quick review of Comment 14
Note that unless the original test case from Comment 1 or Comment 7 still replicates the issue, then the best next step for Comment 14 will be to file a new bug report that includes a new test case that replicates the problem.
(If any of the CC list members of the bug gets a chance to double-check the earlier test cases from Comment 1 and Comment 7, that would be a good step too.)
Thanks in advance!
Bug is not fixed in all cases, see https://bugzilla.xamarin.com/show_bug.cgi?id=52318
Tested in version 22.214.171.124-pre4 this bug remains.
## Note to the Xamarin team
The user from Comment 17 also commented a little later on Bug 52318, so Bug 52318 can be used as the location for the future updates on this issue.
Notice (2018-05-21): bugzilla.xamarin.com will be
switching to read-only mode on Thursday, 2018-05-25 22:00 UTC.
Please join us on
Visual Studio Developer Community and
GitHub to continue tracking
issues. Bugzilla will remain available for reference in read-only mode.
We will continue to work on open Bugzilla bugs and copy them to the new
locations as needed for follow-up. The See Also field
on each Bugzilla bug will be updated with a link to its new location
After Bugzilla is read-only, if you have new information to add for a
bug that does not yet have a matching issue on Developer Community or
GitHub, you can create a follow-up issue in the new location. Copy and
paste the title and description from this bug, and then add your new
details. You can get a pre-formatted version of the title and
In special cases you might also want the comments:
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.