Closed
Bug 1079501
Opened 11 years ago
Closed 7 years ago
[NFC][Contacts] Contacts transferred via NFC do not maintain their Comment field
Categories
(Firefox OS Graveyard :: NFC, defect)
Tracking
(b2g-v2.0 ?, b2g-v2.1 affected, b2g-v2.2 affected, b2g-master affected)
People
(Reporter: Marty, Unassigned)
References
Details
(Whiteboard: [2.1-Daily-Testing],[2.5-aries-test-run-1])
Attachments
(4 files)
Description:
If the user transfers a Contact with a Comment field to another device via NFC, the comment field is not maintained on the second device.
It is expected that the Comment field should be transferred, as it is stored as the 'Note' value in the vCard file.
Repro Steps:
1) Update two Flame devices to BuildID: 20141007000203
2) Activate NFC on both devices from the Settings app
3) On the first device, create a contact that has data in the Comment field
4) Tap the two devices together and transfer the Contact from the first device to the second.
Actual:
The Comment field is not present in the transferred Contact on the second device.
Expected:
The Comment field is transferred properly in the Contact to the second device.
Environmental Variables:
Device: Flame 2.1
BuildID: 20141007000203
Gaia: 7f738edf66b9298bceef8a4981d05d04fd04e540
Gecko: b9d04c58580a
Gonk: 2c909e821d107d414f851e267dedcd7aae2cebf
Version: 34.0a2 (2.1)
Firmware: V180
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
Repro frequency: 7/7
Link to failed test case: https://moztrap.mozilla.org/manage/case/10578/
See attached: logcat
| Reporter | ||
Comment 1•11 years ago
|
||
| Reporter | ||
Updated•11 years ago
|
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(pbylenga)
ni? for Francisco to check if Comment is supported in vcard.
Flags: needinfo?(francisco)
Comment 4•11 years ago
|
||
QAWanted for branch checks.
Blocks: NFC-Gaia
Updated•11 years ago
|
QA Contact: ckreinbring
Comment 5•11 years ago
|
||
The bug repros on Flame 2.2 (engineering and nightly) and Flame 2.1 nightly. The nightlies had a full flash while the engineering had a shallow flash.
Actual result: After being transferred via NFC, a contact with a picture does not retain the picture.
Flame 2.2 engineering
BuildID: 20141008170004
Gaia: 7b92615bdc97e5c675cd385ec68bc5e47e0c5288
Gecko: f0bb13ef0ee4
Platformn Version: 35.0a1
Firmware Version: V180
User Agent: Mozilla/5.0 (Mobile; rv:35.0) Gecko/35.0 Firefox/35.0
Flame 2.2 nightly
BuildID: 20141009040206
Gaia: 7b92615bdc97e5c675cd385ec68bc5e47e0c5288
Gecko: f0bb13ef0ee4
Gonk: 52c909e821d107d414f851e267dedcd7aae2cebf
Platform Version: 35.0a1
Firmware Version: V180
User Agent: Mozilla/5.0 (Mobile; rv:35.0) Gecko/35.0 Firefox/35.0
Flame 2.1 nightly
BuildID: 20141009000203
Gaia: 7e2ef41d3ac98757acaf490b5413fb42061ad3e6
Gecko: 75ebb70f8b38
Gonk: 52c909e821d107d414f851e267dedcd7aae2cebf
Platform Version: 34.0a2
Firmware Version: V180
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
--------------------------------------------------------------------------------------------------------
Unable to attempt repro on Flame 2.1 engineering or 2.0 nightly due to the fact that the device is unable to send or receive via NFC. No response is seen when a transfer is attempted.
Flame 2.1 nightly received a shallow flash while 2.0 nightly was a full flash.
Flame 2.1 engineering
BuildID: 20141008192207
Gaia: 7e2ef41d3ac98757acaf490b5413fb42061ad3e6
Gecko: 75ebb70f8b38
Platform Version: 34.0a2
Firmware Version: V180
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
Flame 2.0 nightly
BuildID: 20141009000201
Gaia: c1f60895e5bcc6a951f3667c2a1e1bd39d393420
Gecko: 4540201b5da0
Gonk: 52c909e821d107d414f851e267dedcd7aae2cebf
Platform Version: 32.0
Firmware Version: V180
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
QA Whiteboard: [QAnalyst-Triage?]
status-b2g-v2.0:
--- → ?
status-b2g-v2.2:
--- → affected
Flags: needinfo?(jmitchell)
Keywords: qawanted
Comment 6•11 years ago
|
||
Alison - NI to you to make a blocking decision
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmitchell) → needinfo?(ashiue)
Comment 7•11 years ago
|
||
Since Comment is not a basic required info for contact, thus I don't want to treat this bug as a blocking issue.
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage+][COM=NFC]
Flags: needinfo?(ashiue)
Comment 8•10 years ago
|
||
This issue also occurs in 3.0 when sharing a contact though the contact app (via Messenger, Email or Bluetooth)
Device: Flame Master
Build ID: 20150317073344
Gaia: 738987bd80b0ddb4ccf853855388c2627e19dcc1
Gecko: 008b3f65a7e0
Gonk: b83fc73de7b64594cd74b33e498bf08332b5d87b
Version: 39.0a1 (Master)
Firmware Version: v188-1
User Agent: Mozilla/5.0 (Mobile; rv:39.0) Gecko/39.0 Firefox/39.0
Updated•10 years ago
|
status-b2g-master:
--- → affected
Comment 9•10 years ago
|
||
This issue also reproduces on latest build of Aries kk v2.5.
Result: The Comment field is not present in the transferred Contact on the second device.
See attchment:Aries_v2.5.3gp & logcat_1548.txt
Device: Aries KK 2.5(Affected)
Build ID 20150814002651
Gaia Revision 39b121515ab8a8c3ea07f26d3ba1dd792e90217c
Gaia Date 2015-08-13 18:25:42
Gecko Revision https://hg.mozilla.org/mozilla-central/rev/4e883591bb5dff021c108d3e30198a99547eed1e
Gecko Version 43.0a1
Device Name aries
Firmware(Release) 4.4.2
Firmware(Incremental) eng.worker.20150813.235011
Firmware Date Thu Aug 13 23:50:19 UTC 2015
Bootloader s1
Comment 10•10 years ago
|
||
Updated•10 years ago
|
QA Whiteboard: [QAnalyst-Triage+][COM=NFC] → [QAnalyst-Triage+][COM=NFC][MGSEI-Triage+]
Whiteboard: [2.1-Daily-Testing] → [2.1-Daily-Testing],[2.5-aries-test-run-1]
Updated•10 years ago
|
QA Whiteboard: [QAnalyst-Triage+][COM=NFC][MGSEI-Triage+] → [QAnalyst-Triage+][COM=NFC][MGSEI-Triage+][Low_QA]
Comment 11•7 years ago
|
||
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•