1387195 - History panel doesn't refresh after Sign in with sync completed

Status: NEW

(Firefox for iOS :: Home screen, defect, P3)

Description

[ugarlapati]

If user haven’t signed in, and user is in history tab. Now from history tab user went to settings screen and logged in, once successful sync, user dismissed settings screen. Now user will be in history tab, noticed history is not visible. History will be visible if user switches between the tabs I.e., top site, bookmarks etc

Steps to reproduce: History (Only in iPhone, iPad is working fine)
1. Open the app, make sure user didn’t logged in.
2. Open history tab
3. Go to settings screen from bottom menu tray.
4. Sign in to the account
5. Wait until app syncs completely
6. Dismiss the settings screen.
7. As user went from history tab to settings screen, user will be in history tab.
8. Noticed app not showing synced history
9. Switch between top sites / bookmarks and then go to history tab. Now history is displaying.

Note: If user is in any other screen and sign in, this issue won’t produce.

Comment 1

[u604692]

Hey guys, I can not reproduce this issue running the latest code from master branch, as of 10/26/17.  Here is a video of what I am seeing, trying to follow steps illustrated by ugarlapati: [https://www.youtube.com/watch?v=LQo07kpTA3c]

Thoughts?  Thanks.

Comment 2

[Farhan Patel [:farhan]]

Thanks for the report!

Simon is this a valid bug. Are you able to reproduce?

Comment 3

[Simon Basca [:SimonB]]

Hey Usha. I am unable to reproduce this on the latest master 73081c03882, beta 10.0(7473) and on release 9.3(7374). Can you please let us know on what build and device are you reproducing this issue?

Comment 4

[ugarlapati]

Hi Simon. With the recent UI change, this scenario doesn't exist. As the webpage is default to support.mozilla.org, settings button is not visible until user taps on address bar. Earlier webpage is set to empty address and menu button is visible.

Comment 5

[Simon Basca [:SimonB]]

If the scenario causing the issue no longer exists and this is not reproducible on the latest master, beta and release, does it make sense to mark this as resolved - worksforme?