1120866 - [FFOS2.0][Woodduck][3rd APK][ConnectA2 V017h] The connectA2 still possible to send/receive message after changing the SIM card.

Status: RESOLVED WONTFIX

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

Description

[sync-1]

PR Reporter:邢艳
 contact:0752-2639551(61551)
 		
 
  DEFECT DESCRIPTION:
 >The connectA2 still possible to send/receive message after changing the SIM card.
 
  REPRODUCING PROCEDURES:
 1.Register to application using SIM card 1,send and receive message with a contact.
 2.Then turned off device, change the SIM card 2 .
 3.When turned ON device it still possible to send and receive message with the same contact.--ko
 
  EXPECTED BEHAVIOUR:
 >Should prompt users to register again with the new SIM card.
 
  ASSOCIATE SPECIFICATION:
 
  TEST PLAN REFERENCE:
 
  TOOLS AND PLATFORMS USED:
 
  USER IMPACT:
 
  REPRODUCING RATE:
 
  For FT PR, Please list reference mobile's behavior:

Comment 1

[Shally Li（leave from Mozilla）]

I can repro this bug on Woodduck v2.0 and Flame v2.0&2.1&2.2.
See attachment: connectA2_v2.0_1515.MP4 and logcat_v2.0_1515.txt.
Reproduce rate: 4/4.

Repro STR:
1.Connect wifi and download ConnectA2 app (Version:017h) from Marketplace.
2.Register to this app using SIM1 card,send and receive message with a contact.
2.Then turned off device and change the SIM card to slot 2.
3.When turned on device and open this app.
**It still can send and receive message with the same contact.

Note:After you register,
(1)Insert a other SIM card in device,you can send and receive message with the same contact in ConnectA2.And it doesn't prompt user to register again.
(2)Don't insert SIM card in device,you also can send and receive message with the same contact in ConnectA2.And it doesn't prompt user to register again.

Woodduck 2.0 build:
Gaia-Rev        ddb406ebdb34ca6717eda14297dea98f26f1f412
Gecko-Rev       20943fe7b54c63a375952fbd8dd396a22ee893e7
Build-ID        20150114050313
Version         32.0
Device-Name     jrdhz72_w_ff
FW-Release      4.4.2
FW-Incremental  1421183152
FW-Date         Wed Jan 14 05:06:17 CST 2015

Flame 2.0 build:
Gaia-Rev        31d6c9422cd0a8213df9f96019c9ab7168ec3ab3
Gecko-Rev       https://hg.mozilla.org/releases/mozilla-b2g32_v2_0/rev/f2b6017e84eb
Build-ID        20150113160201
Version         32.0
Device-Name     flame
FW-Release      4.4.2
FW-Incremental  eng.cltbld.20150113.192825
FW-Date         Tue Jan 13 19:28:37 EST 2015
Bootloader      L1TC000118D0

Flame 2.1 build:
Gaia-Rev        6957ac8a322234ec99c8abb7cc18dc6a2e0176db
Gecko-Rev       https://hg.mozilla.org/releases/mozilla-b2g34_v2_1/rev/6600eba54256
Build-ID        20150113161204
Version         34.0
Device-Name     flame
FW-Release      4.4.2
FW-Incremental  eng.cltbld.20150113.192836
FW-Date         Tue Jan 13 19:28:47 EST 2015
Bootloader      L1TC000118D0

Flame 2.2 build:
Gaia-Rev        7c5b27cad370db377b18a742d3f3fdb0070e899f
Gecko-Rev       https://hg.mozilla.org/releases/mozilla-b2g37_v2_2/rev/748b20315f75
Build-ID        20150113162504
Version         37.0a2
Device-Name     flame
FW-Release      4.4.2
FW-Incremental  eng.cltbld.20150113.194114
FW-Date         Tue Jan 13 19:41:25 EST 2015
Bootloader      L1TC000118D0

Comment 2

[Shally Li（leave from Mozilla）]

Attachment: logcat_v2.0_1515.txt

Comment 3

[Shally Li（leave from Mozilla）]

Attachment: connectA2_v2.0_1515.MP4

Comment 4

[Shally Li（leave from Mozilla）]

Sorry to update for Comment 2.
I can't input number to register becase of Bug 1120792,so I skip it on Flame v2.2.

Comment 5

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

This is a 3rd party app issue. move to correct product.

Comment 6

[Wesly Huang (EPM)]

Hi Reporter:

Please read & follow P9 & P10 in attached process for App issue submission, for example:

1. set correct product and component
2. cc right people in the beginning (pls update this one, too)
3. confirm in issue description: if this can be reproduced w/ Mozilla reference device (ex: Flame), or reference image like Mozilla 2.0m build (pls also update this now if not mentioned in above)

Thanks.

Comment 7

[Wesly Huang (EPM)]

Attachment: App issue submission process (P9 & P10)

Comment 8

[Michael Ellis]

the WA API only needs MCC and MNC for registration, and does not recheck the SIM after registration.  This performance is by design. The experience is not broken for the user and the app is behaving as intended by the developer.  Closing this bug as Won't Fix