Bug 59514 - iOS: Listview Footer disappears on Navigation
Summary: iOS: Listview Footer disappears on Navigation
Status: CONFIRMED
Alias: None
Product: Forms
Classification: Xamarin
Component: Forms (show other bugs)
Version: 2.4.0
Hardware: PC Mac OS
: Normal normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2017-09-15 11:44 UTC by Vivek Suman
Modified: 2017-10-03 15:19 UTC (History)
3 users (show)

See Also:
Tags: listview, footer, onappearing, ac
Is this bug a regression?: ---
Last known good build:


Attachments

Description Vivek Suman 2017-09-15 11:44:41 UTC
On iOS, the footer appears but subsequent navigation to different page and back makes footer invisible.

### Steps to reproduce issue on Windows
1. Create a Listview without any footer
2. Add a view to the footer myLV.Footer = myGrid in OnAppearing;
3. Navigate to another page.
4. Back to Listview page.

### Expected Results
The footer should remain visible.


### Actual Results
The footer is not visible after navigating back to ListView page.


### Version info
Reproduced with Forms 2.3.4.270 and Forms 2.3.5.256-pre1
Comment 1 Paul DiPietro [MSFT] 2017-09-15 18:31:34 UTC
Just based on what you've stated, it seems like this doesn't occur for me using the a very basic page with a ListView where its footer contains a Grid (the Grid contains only a Label for visibility confirmation). Footer = Grid is done in OnAppearing. There wasn't an apparent change regardless of whether or not the ListView needed to scroll. 

Would you mind uploading a reproduction so we can see the exact code you're using in case there are any differences in particular, along with what device/emulator you're attempting to run the app on? Thanks in advance!
Comment 2 Vivek Suman 2017-09-19 13:05:04 UTC
It seems that adding a Scrollview to the footer is creating this issue. I have added the demo in Repository https://github.com/vksuman/Xamarin.

Simulator Version: iPhone 6 - iOS 10.2
Comment 3 Vivek Suman 2017-10-03 10:55:20 UTC
It's still the same with iOS 11.

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