Closed
Bug 1029200
Opened 10 years ago
Closed 10 years ago
[B2G][Settings][Contacts]Dimmed homescreen with no apps display after selecting Done button in Check settings area for failed Gmail import due to no internet connectivity
Categories
(Firefox OS Graveyard :: Gaia::System::Window Mgmt, defect)
Tracking
(blocking-b2g:2.0+, b2g-v2.0 affected, b2g-v2.1 affected)
RESOLVED
DUPLICATE
of bug 1023812
blocking-b2g | 2.0+ |
People
(Reporter: mclemmons, Assigned: alive)
References
()
Details
(Whiteboard: [2.0-flame-test-run-2][systemsfe])
Attachments
(1 file)
1.46 KB,
text/plain
|
Details |
User taps Contacts App with internet connectivity enabled, then selects import contacts from Gmail. While the import loading page displays, quickly slide down the notification bar and disable internet connectivity. User gets a message that an Internet connection is required with a logo of a device in blue borders with an exclamation point in the middle with Check Settings button. Or user gets the Google Request for Permission Page to accept or cancel. When canceled, the internet connection is required screen displays. When the user selects check settings and goes to the Settings menu showing only Network & Connectivity and user selects Done, the homescreen displays with no icons in a dimmed manner.
Prerequisites:
1. WiFi or Data connection enabled
Repro Steps:
1) Update a Flame to 20140623000201
2) Tap Contacts App and select gear icon
3) Tap import contacts and log in to Gmail (if not already logged in)
4) Slide notification bar and disable Wifi or Data
5) User will get either the Google Request for Permission Page or FFOS Access to internet required message
6) If Google request page reached, select Accept and observe step 5 above
7) Tap check settings then Done button
8) Observe device behavior
Actual:
Dimmed homescreen with no apps display.
Expected:
Return to screen with FFOS Access to internet required message
Notes:
Repro frequency: (10/10, 100%)
Link to failed test case: None. Issue found exploratory testing around existing test case.
See attached:
a) video = https://www.youtube.com/watch?v=x_lgosY_kRQ
b) Flame logcat unavailable due to https://bugzilla.mozilla.org/show_bug.cgi?id=1010993
c) Open C logcat provided instead of Flame logcat described in b) above
Environmental Variables:
Device: Flame 2.0
Build ID: 20140623000201
Gaia: 729f214b887ce8efe7d870145d31acb2c6427817
Gecko: 117ba3eda4d2
Version: 32.0a2 (2.0)
Firmware Version: v121-2
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
Reporter | ||
Updated•10 years ago
|
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
This issue DOES reproduce on Flame 2.1, Buri 2.1, Open C 2.1, Buri 2.0, and Open C 2.0
If the user selects check settings and then done in rapid succession they will be brought to a blank, and dimmed homescreen. This can be bypassed by closing all apps in card view
Flame 2.1
Environmental Variables:
Device: Flame Master
Build ID: 20140623040202
Gaia: bd5065ced020014df5fd45259fba1ac32d65673b
Gecko: 366b5c0c02d3
Version: 33.0a1 (Master)
Firmware Version: v121-2
User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0
Open_C 2.1
Environmental Variables:
Device: Open_C Master
Build ID: 20140623040202
Gaia: bd5065ced020014df5fd45259fba1ac32d65673b
Gecko: 366b5c0c02d3
Version: 33.0a1 (Master)
Firmware Version: P821A10V1.0.0B06_LOG_DL
User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0
Buri 2.1
Environmental Variables:
Device: Buri Master
Build ID: 20140623073039
Gaia: bd5065ced020014df5fd45259fba1ac32d65673b
Gecko: 335b6610fe0c
Version: 33.0a1 (Master) MOZ
Firmware Version: v1.2device.cfg
User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0
The user does not need to tap anything in rapid succession for 2.0 devices, this issue will occur first try
If the user selects check settings and then done they will be brought to a blank, and dimmed homescreen. This can be bypassed by closing all apps in card view.
Buri 2.0
Environmental Variables:
Device: Buri 2.0
BuildID: 20140623063006
Gaia: 84ca0fe0a86d039f6d99cb562f52ef55045dee1d
Gecko: cef223bae66b
Version: 32.0a2 (2.0) MOZ
Firmware Version: v1.2device.cfg
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
Open_C 2.0
Environmental Variables:
Device: Open C 2.0
Build ID: 20140623000201
Gaia: 729f214b887ce8efe7d870145d31acb2c6427817
Gecko: 117ba3eda4d2
Version: 32.0a2 (2.0)
Firmware Version: P821A10V1.0.0B06_LOG_DL
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
_________________________________________________________________________________________
This issue does NOT reproduce on Flame 1.4, Buri 1.4 or Open C 1.4
The user is taken to an error page that states "Network connection unavailable". They do not have the option to "Check settings" and are unable to repro this bug
Buri 1.4
Environmental Variables:
Device: Buri 1.4
BuildID: 20140623063003
Gaia: 3419a1f68aaf64a0688685bce42d4173b6125597
Gecko: ccf2fada2574
Version: 30.0 (1.4) MOZ
Firmware Version: v1.2device.cfg
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0
Flame 1.4
Environmental Variables:
Device: Flame 1.4
Build ID: 20140623000201
Gaia: 3419a1f68aaf64a0688685bce42d4173b6125597
Gecko: 34ecc9af3560
Version: 30.0 (1.4)
Firmware Version: v121-2
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0
Open_C 1.4
Environmental Variables:
Device: Open_C 1.4
Build ID: 20140623000201
Gaia: 3419a1f68aaf64a0688685bce42d4173b6125597
Gecko: 34ecc9af3560
Version: 30.0 (1.4)
Firmware Version: P821A10V1.0.0B06_LOG_DL
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0
Comment 2•10 years ago
|
||
Jason this issue leaves the user in a state where the screen is dim and no apps appear to be present on the "homescreen".
I'm thinking this issue should be nominated 2.0? but the user can easily get out of this bug by tapping the home button on the device.
This page "No access to the Internet right now. Check settings" appears to be a newly added feature because this page does not show up on 1.4. I am unsure of who the owner should be to need info them. Can you point me in the right direction?
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker) → needinfo?(jsmith)
Comment 3•10 years ago
|
||
I think we need to nail down STR here - I think a lot of these steps aren't relevant to the bug. Can we find reduced STR?
Blocks: 1015336
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage+][VH-FL-blocking-][VH-FC-blocking?]
Component: Gaia::Contacts → Gaia::Homescreen
Flags: needinfo?(jsmith)
Keywords: steps-wanted
Updated•10 years ago
|
QA Whiteboard: [QAnalyst-Triage+][VH-FL-blocking-][VH-FC-blocking?] → [VH-FL-blocking-][VH-FC-blocking?]
Comment 4•10 years ago
|
||
From the video it appears we have no homescreen at all. I don't think this should block bug 1015336 as it's not related to homescreen work.
No longer blocks: 1015336
Component: Gaia::Homescreen → Gaia::System::Window Mgmt
Updated•10 years ago
|
QA Whiteboard: [VH-FL-blocking-][VH-FC-blocking?]
Comment 5•10 years ago
|
||
This issue can be reproduced from the new page ("No access to the Internet right now. Check settings") with some different steps.
1) Update a Flame to 20140623000201
2) Tap Contacts App and select gear icon
3) Enable wifi
4) Select Facebook "Sync Friends"
5) Disable wifi
6) Press "Log in" on the Facebook page
7) Press "Check Settings" on the new page
8) Device should be in the Settings menu, press "Done"
Result:
Dimmed homescreen with no apps display.
Updated•10 years ago
|
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmitchell)
Comment 6•10 years ago
|
||
The STR is tougher to hit, but the impact of this bug is really bad, as this looks like the homescreen is busted.
blocking-b2g: --- → 2.0?
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage+][lead-review+]
Whiteboard: [2.0-flame-test-run-2] → [2.0-flame-test-run-2][systemsfe]
Assignee | ||
Comment 7•10 years ago
|
||
The root cause seems be same as bug 1023812. Not sure why it's still happening..
Updated•10 years ago
|
Assignee: nobody → alive
blocking-b2g: 2.0? → 2.0+
Comment 10•10 years ago
|
||
bug 1023812 should have fixed this problem, however, it was landed by 6-24, that's why it can be reproduced on 20140623xxxx build.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•