1040332 - [B2G][NFC] Receiving a call mid-swipe and completing the swipe causes the file to send.

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: NFC, defect)

Description

[Dean R. Gomez (DeanG)]

Attachment: Logcat_Swipe_Call.txt

Description:
When a user attempts to share a file via NFC, begins to swipe the file to transfer to another device, receives a call, keeps their finger on the screen, and while on the incoming call screen the user completes the swipe, the file will send to the other phone.

NOTE: Occasionally, just removing the finger from the incoming call screen will send the file due to it registering as a full swipe.

Prerequisites: Have an extra device with NFC, an image file to transfer from the device under test (DUT), and another device that can make calls. Ensure both NFC devices have NFC enabled and that the DUT has a SIM ready to receive calls.

Repro Steps:
1) Update a Flame to 20140717000201
2) Launch the Gallery app on the DUT.
3) Select an image file.
4) Hold both devices with NFC back-to-back to one another.
5) Begin to swipe up on the image when prompted, but swipe only halfway and keep your finger on the screen.
6) Make a call to the DUT.
7) On the incoming call screen on the DUT, complete the swipe and drag your finger to the top of the screen.
8) Observe the screen.

Actual:
A notification stating the "File Transfer" has started appears and the file is transferred.
Expected:
No notification appears and no file is sent as the user is no longer on the NFC sharing screen.

2.0 Environmental Variables:
Device: Flame 2.0 (273MB)
Build ID: 20140717000201
Gaia: aa4f795b81c6147d67c4f06009e166debcf8856e
Gecko: 0ec0b9ac39f0
Version: 32.0a2 (2.0) 
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.

Repro frequency: 4/4 - 100%
See attached: Logcat_Swipe_Call.txt, Video: http://youtu.be/HINxva6ERsE

Comment 1

[Dean R. Gomez (DeanG)]

NOTE: Could not check Flame 1.4, Buri 1.3, Buri 1.4, Buri 2.0, Buri 2.1, Open_C 1.4, Open_C 2.0, Open_C 2.1, Flame Base v122, and Flame Base v121-2 due to NFC not being an available feature.


This issue DOES occur on Flame 2.0 (512MB).


Flame 2.0 (512MB)

2.0 Environmental Variables:
Device: Flame 2.0
Build ID: 20140717000201
Gaia: aa4f795b81c6147d67c4f06009e166debcf8856e
Gecko: 0ec0b9ac39f0
Version: 32.0a2 (2.0) 
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.


Result: The file is sent and a notification appears over the incoming call screen.

---------------------------------------------------------------------------------------------------------

This issue DOES NOT occur on Flame 2.1 (273MB).


Flame 2.1 (273MB)

2.1 Environmental Variables:
Device: Flame Master
Build ID: 20140717040202
Gaia: Unknown
Gecko: a74600665875
Version: 33.0a1 (Master)
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0


Result: The screen is shown to take the user to the vertical homescreen before displaying the incoming call screen. The user cannot send the file.

Comment 2

[Jason Smith [:jsmith]]

Kevin - Couple of things:

1. Why is this tagged with the regression keyword? Isn't this a bug in a new feature?
2. We need a blocking triage analysis here

Comment 3

[KTucker [:KTucker][Inactive 3/4/2016]]

1. I have no idea why the regression keyword was added to this issue. I should have caught that.
2. This issue seems minor to me and more of a tester bug. The user is purposely sliding up on the screen to send the file while there is an incoming call. I really don't see too much of an issue here.

I don't think this should be nominated as a blocker.

Comment 4

[BMO Automation]

Firefox OS is not being worked on