1105971 - [FFOS2.0][Woodduck][3rd apk][Twitter & Facebook]Black screen was displayed when used China Mobile/China Unicom sim card to login Twitter/Facebook.

Status: RESOLVED WONTFIX

(Tech Evangelism Graveyard :: Preinstalled B2G Apps, defect, P2)

Description

[sync-1]

Created an attachment (id=1015517)
 log_ChinaUnicom.part01
 
 DEFECT DESCRIPTION:
 ->Black screen was displayed when used China Mobile/China Unicom sim card to login Twitter/Facebook.
 
 REPRODUCING PROCEDURES:
 ->1.Insert China Mobile/China Unicom sim card to handset.
 ->2.Open handset and enable data connection.
 ->3.Clicked Twitter, black screen was displayed, and notification about "unable to login Twitter" was not displayed. ===>KO1
 ->4.Clicked Facebook, black screen was displayed, and notification about "unable to login Facebook" was not displayed.===>KO2
 
 EXPECTED BEHAVIOUR:
 ->When used China Mobile/China Unicom sim card to login Twitter/Facebook:
 (a)Black screen should not display.
 (b)Notification about "unable to login Twitter/Facebook" should display.
 
  ASSOCIATE SPECIFICATION:
 
  TEST PLAN REFERENCE:
 
  TOOLS AND PLATFORMS USED:
 
  USER IMPACT:
 
  REPRODUCING RATE:
 
  For FT PR, Please list reference mobile's behavior:
 
 何嘉玲：0752-2611649（61649）

Comment 1

[sync-1]

Attachment: log_ChinaUnicom.part01

Comment 2

[sync-1]

Attachment: log_ChinaMobile

Comment 3

[sync-1]

Attachment: log_ChinaUnicom.part01

Comment 4

[sync-1]

Attachment: log_ChinaUnicom.part02

Comment 5

[sync-1]

Attachment: screen_facebook

Comment 6

[sync-1]

Attachment: screen_Twitter

Comment 7

[Josh Cheng [:josh]]

Hi Norry,
qawanted for Woodduck 2.0M and Flame 2.0/2.1/2.2. Thanks!

Comment 9

[Norry.L.F(Leave from Mozilla)]

Attachment: V2.0.png

Using 3G SIM Card, this bug can be easily repro on Flame 2.0, on Flame 2.1/2.2, notification about "unable to login Facebook" will pop up after waiting 3 or more minutes.

I just test it using CU SIM card on Flame 2.0/2.1/2.2(Flame can't recognize CMCC 3G network, just recognize 2G);

On woodduck, my device just can recognize 2G network using CU and CMCC 3G SIM card, and can't verify this bug according to reporter's environment. But if using 2G network, the bug can be repro on Woodduck 2.0M and Flame 2.0/2.1/2.2


Woodduck build:
Gaia-Rev        0e4a94fca05719b49139a7d5267e5fb3ea5c3449
Gecko-Rev       93efc8b4155f0a4a50eaad19acbb95ec24139e63
Build-ID        20141203050313
Version         32.0
Device-Name     jrdhz72_w_ff
FW-Release      4.4.2
FW-Incremental  1417554324
FW-Date         Wed Dec  3 05:05:48 CST 2014
------------------
Flame 2.0:
Gaia-Rev        8d1e868864c8a8f1e037685f0656d1da70d08c06
Gecko-Rev       https://hg.mozilla.org/releases/mozilla-b2g32_v2_0/rev/c756bd8bf3c3
Build-ID        20141202000201
Version         32.0
Device-Name     flame
FW-Release      4.4.2
FW-Incremental  eng.cltbld.20141202.034707
FW-Date         Tue Dec  2 03:47:18 EST 2014
Bootloader      L1TC00011880
------------------
FLame2.1 build:
Gaia-Rev        ccb49abe412c978a4045f0c75abff534372716c4
Gecko-Rev       https://hg.mozilla.org/releases/mozilla-b2g34_v2_1/rev/18fb67530b22
Build-ID        20141202001201
Version         34.0
Device-Name     flame
FW-Release      4.4.2
FW-Incremental  eng.cltbld.20141202.034824
FW-Date         Tue Dec  2 03:48:34 EST 2014
Bootloader      L1TC00011880
------------------
FLame2.2 build:
Gaia-Rev        725685831f5336cf007e36d9a812aad689604695
Gecko-Rev       https://hg.mozilla.org/mozilla-central/rev/2c9781c3e9b5
Build-ID        20141202040207
Version         37.0a1
Device-Name     flame
FW-Release      4.4.2
FW-Incremental  eng.cltbld.20141202.072347
FW-Date         Tue Dec  2 07:23:58 EST 2014
Bootloader      L1TC00011880

Comment 10

[Norry.L.F(Leave from Mozilla)]

Attachment: logcat_1456.txt

log on Flame 2.0

Rate: 3/3
Found at: 14:56

Comment 11

[Norry.L.F(Leave from Mozilla)]

Attachment: V2.1&V2.2.png

Comment 12

[Norry.L.F(Leave from Mozilla)]

Hi Hubert,
Could you help to verify this bug on woodduck 2.0m using 3G network? 
Thank you

Comment 13

[Josh Cheng [:josh]]

Hi Peipei,
Can you help to check whether the problem still exist? Thanks!

Comment 14

[Peipei Cheng (needinfo if you need my action)]

Yes, it's still reproducible on 2.0 and 2.0m. 

The black screen is actually a loading screen displayed when web app content is not retrieved.

As you know, Twitter and Facebook are blocked in China mainland, that's why it keeps trying to connect. After it get time out, an error msg should appear. 

But on Flame 2.0 and woodduck 2.0, no error msg appears after connecting to twitter/facebook get timeout. We may want to check this.

Comment 15

[Josh Cheng [:josh]]

Wontfix as this not happen on post 2.1 version per comment 9.