Closed
Bug 1066327
Opened 10 years ago
Closed 6 years ago
[NFC] User is prompted file could not be received but will receive the file after current transfer is completed
Categories
(Firefox OS Graveyard :: NFC, defect)
Tracking
(b2g-v2.0 affected, b2g-v2.1 affected, b2g-v2.2 affected)
RESOLVED
WONTFIX
People
(Reporter: KTucker, Unassigned)
References
()
Details
(Whiteboard: [2.1-flame-test-run-2])
Attachments
(1 file)
291.69 KB,
text/plain
|
Details |
Description: If the user is currently receiving a file via NFC and is then sent another file, they will be prompted "File could not be received". However, after the user receives the first file, they will notice the second file will be downloaded and received. Prerequisite: Turn on NFC on both test devices. Repro Steps: 1) Updated Flame to Build ID: 20140910000202 2) Tap Device A and Device B together and send Device B a video. 3) While Device B is receiving the video, tap the phones together again and send Device B another video. Actual: Device B will receive a notification that the "File could not be received". Device A will receive a notification that "The transfer has started". After the first file has been received, Device B will receive the second file. Expected: The notification should say something like "File will be received after the current transfer has completed." Environmental Variables: Device: Flame 2.1 (Full Flash was used) BuildID: 20140910000202 (319mb) Gaia: 79dc972d637ff5ef7667b231e93118b4ed83ba9c Gecko: 0890010015a2 Version: 34.0a2 (2.1) Firmware: V123 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0 Notes: Repro frequency: 100% Link to failed test case: https://moztrap.mozilla.org/manage/case/10582/ See attached: video clip, logcat
Reporter | ||
Comment 1•10 years ago
|
||
This issue also occurs on the Flame 2.2(319mb), Flame 2.1(512mb), Flame 2.0(319mb)(JB) and Flame 2.0(319mb)(KK). Flame 2.2 Environmental Variables: Device: Flame Master (319mb) BuildID: 20140910040203 Gaia: 8e02f689b0fc39cb6ccdc22d02ed7e219c58faa7 Gecko: 152ef25e89ae Version: 35.0a1 (Master) Firmware Version: v123 User Agent: Mozilla/5.0 (Mobile; rv:35.0) Gecko/35.0 Firefox/35.0 Flame 2.1 Environmental Variables: Device: Flame 2.1 BuildID: 20140910000202 (512mb) Gaia: 79dc972d637ff5ef7667b231e93118b4ed83ba9c Gecko: 0890010015a2 Version: 34.0a2 (2.1) Firmware: V123 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0 Flame 2.0 Environmental Variables: Device: Flame 2.0 (319mb)(JB) BuildID: 20140910000203 Gaia: 3f4c635106c5364228782d12b1cb76b0c105b971 Gecko: 02a5b9234c13 Version: 32.0 (2.0) Firmware Version: v123 User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0 Flame 2.0 Environmental Variables: Device: Flame 2.0 (319mb)(KK) BuildID: 20140910000203 Gaia: 3f4c635106c5364228782d12b1cb76b0c105b971 Gecko: 02a5b9234c13 Version: 32.0 (2.0) Firmware Version: v123 User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0 ---------------------------------------------------------------------- This issue cannot be verified on the Flame 1.4 because NFC was not supported in 1.4 Flame 1.4 Environmental Variables: Device: Flame 1.4 (319mb) BuildID: 20140910000204 Gaia: 6018a1c18f0c3eab25aac2ba3064904740591dd2 Gecko: 90e68c490bf9 Version: 30.0 (1.4) Firmware Version: v123 User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0 ---------------------------------------------------------------------- This issue cannot be verified on Open C devices because it is not NFC capable.
QA Whiteboard: [QAnalyst-Triage?]
status-b2g-v2.0:
--- → affected
status-b2g-v2.2:
--- → affected
Flags: needinfo?(dharris)
Reporter | ||
Updated•10 years ago
|
Not nominating this as a 2.1? blocker. The user is able to transfer files properly, they just get a screen that tells them an error occurred when it didn’t.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(dharris)
Comment 3•6 years ago
|
||
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•