Closed Bug 1094527 Opened 10 years ago Closed 10 years ago

[NFC] Cannot share with other device through NFC, does not go to sharing UI

Categories

(Firefox OS Graveyard :: NFC, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(b2g-v2.0 unaffected, b2g-v2.1 unaffected, b2g-v2.2 affected)

RESOLVED INVALID
Tracking Status
b2g-v2.0 --- unaffected
b2g-v2.1 --- unaffected
b2g-v2.2 --- affected

People

(Reporter: jlee, Unassigned)

References

()

Details

(Keywords: regression, Whiteboard: [2.1-exploratory-3])

Attachments

(1 file)

Attached file NFClogcat.txt
Description:
Tapping two NFC enabled devices together when one user is on website will cause devices to vibrate, but does not go to "swipe up" sharing UI. Users cannot share media through NFC. From 2.2 device.
   
Repro Steps:
1) Update a Flame device to BuildID: 20141105040206
2) Have two devices (One device must be 2.2)
3) Go to Settings > turn on NFC on both devices
4) On device 1 (2.2), open Browser and open a website
5) Tap both devices together
6) Notice if device 1 has "swipe up"/share UI to share site with device 2
  
Actual:
With two NFC enabled devices and device 1 on a website in browser, tapping the devices together will result in them vibrating, but will not bring up "swipe up" sharing UI. User cannot share website through NFC. On 2.2.
  
Expected: 
With two NFC enabled devices and device 1 on a website in browser, tapping the devices together will result in them vibrating and brings up "swipe up" sharing UI. User can share website (plus any other NFC shareable media) through NFC.
  
Environmental Variables:
Device: Flame 2.2 Master (319mb)(Kitkat Base)(Shallow Flash)
BuildID: 20141105040206
Gaia: 7c9e7cabbde941b976e0e40a3a1d94e21aa9c5e9
Gecko: 62990ec7ad78
Gonk: 
Version: 36.0a1 (2.2 Master)
Firmware: V188-1
User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0
  
Notes: Same issue occurs when trying to share photo through NFC.
2.2 > 2.2 = issue occurs
2.2 > 2.1 = issue occurs
2.2 > 2.0 = issue occurs
2.1 > 2.2 = 2.1 can send site/media to 2.2
2.0 > 2.2 = 2.0 can send site/media to 2.2
  
Repro frequency: 100%
See attached: video clip (http://youtu.be/AzZOreVu6mo), logcat (NFClogcat.txt)
Issue does not occur on 2.0 or 2.1.

With two NFC enabled devices and device 1 on a website in browser, tapping the devices together will result in them vibrating and brings up "swipe up" sharing UI. User can share website (plus any other NFC shareable media) through NFC.

Device: Flame 2.0 (319mb)(Kitkat Base)(Shallow Flash)
BuildID: 20141105000201
Gaia: fe2167fa5314c7e71c143a590914cbf3771905a8
Gecko: 093de6b632c5
Version: 32.0 (2.0)
Firmware: V188-1
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Device: Flame 2.1 (319mb)(Kitkat Base)(Shallow Flash)
BuildID: 20141105001204
Gaia: 154da5e17029a51002d5d9b7df39563d509edde6
Gecko: 3b0c3580a58d
Version: 34.0 (2.1)
Firmware: V188-1
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(dharris)
Nominating to block 2.2. The user should be able to share Photos and and websites without any issue. basic functionality broken. also a regression
blocking-b2g: --- → 2.2?
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(dharris)
QA Contact: ddixon
Is this something you can help?
Flags: needinfo?(gduan)
QA Whiteboard: [COM=NFC]
Neither George and I cannot reproduce on latest build.
Also I cannot see too much useful informatio in the logcat.

Could Jaramiah enable the NFC debug in Settings->Developer->enable NFC debug and help to try this again?

Thanks
Flags: needinfo?(gduan) → needinfo?(jlee)
QAWANTED: is it still reproducible?
Keywords: qawanted
Issue DOES reproduce in the latest Flame 2.2 Central build (Tinderbox Engineering).  

Device: Flame 2.2
BuildID: 20141111042605
Gaia: 6af3a8a833eb8bb651e8b188cb3f3c3a43bb4184
Gecko: c60fc2c11c0e
Version: 36.0a1 (2.2)
Firmware: V188-1
User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0

I am currently looking for a regression window for this issue.
Flags: needinfo?(jlee)
Keywords: qawanted
B2G Inbound Regression Window: 

Last Working

Device: Flame 2.2
BuildID: 20141016022641
Gaia: 5c636a7a54b2c86d8ff6bc1aa1e5f9594c7bc586
Gecko: f461eb1653f1
Version: 36.0a1 (2.2)
Firmware: V188-1
User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0

First Broken

Device: Flame 2.2
BuildID: 20141016031842
Gaia: 5c636a7a54b2c86d8ff6bc1aa1e5f9594c7bc586
Gecko: c6e8d12832f7
Version: 36.0a1 (2.2)
Firmware: V188-1
User Agent: Mozilla/5.0 (Mobile; rv:36.0) Gecko/36.0 Firefox/36.0

Last Working Gaia and First Broken Gecko
Issue DOES occur here. 
Gaia: 5c636a7a54b2c86d8ff6bc1aa1e5f9594c7bc586
Gecko: c6e8d12832f7

Last Working Gecko and First Broken Gaia
Issue DOES NOT occur here. 
Gaia: 5c636a7a54b2c86d8ff6bc1aa1e5f9594c7bc586
Gecko: f461eb1653f1

Gecko Pushlog: 
http://hg.mozilla.org/integration/b2g-inbound/pushloghtml?fromchange=f461eb1653f1&tochange=c6e8d12832f7
QA Whiteboard: [COM=NFC] → [COM=NFC] [QAnalyst-Triage?]
Flags: needinfo?(jmitchell)
2 bugs in this pushlog, both by Yoshi; can you take a look.
QA Whiteboard: [COM=NFC] [QAnalyst-Triage?] → [COM=NFC] [QAnalyst-Triage+]
Flags: needinfo?(jmitchell) → needinfo?(allstars.chh)
QA Contact: ddixon
These changes also involve nfcd change, I guess you didn't do full flash, and only updated Gecko+Gaia.

Ni? to Alison to confirm this.
Flags: needinfo?(allstars.chh) → needinfo?(ashiue)
Close this bug since this issue does not occur when full flash 2.2.
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(ashiue)
Resolution: --- → INVALID
blocking-b2g: 2.2? → ---
QA Whiteboard: [COM=NFC] [QAnalyst-Triage+] → [QAnalyst-Triage+]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: