1115630 - [Bluetooth File Transfer] Cannot get connected device in the second time while receiving file from the same remote device

Status: RESOLVED WORKSFORME

(Firefox OS Graveyard :: Bluetooth, defect)

Description

[[e-mail], [e-mail]]

STD:
1. Enable Bluetooth, Enable visible
2. Send a file from the remote device.
3. See notification/prompt and confirm to receive file.
4. Wait the receiving file completely.
Repeat step 2.

Actual:
There is no any prompt for the second incoming file request.

Expected:
There will be showing a prompt for each incoming file request.

Comment 1

[[e-mail], [e-mail]]

After investigation, it's normal to receive 'bluetooth-opp-receiving-file-confirmation' event. For every receiving file, we will get the connected device for reaching the device name. In the second time, there is no connected device in the req.onsuccess of API getConnectedDevices(). It make the functionality broken in part of receiving file via Bluetooth.

Jamin, could you please help to investigate the issue? Thanks.

Comment 2

[Jamin Liu [:jaliu][:Jamin]]

I'll take a look.
Thank you for the investigation. :)

Comment 3

[Pi Wei Cheng [:piwei] (inactive)]

I was able to reproduce this bug on a 12/24 central build, but the issue is no longer reproducible on latest central.

When reproducing the bug, DUT doesn't get a prompt on all subsequent attempts to receive a file via bluetooth after the first attempt, therefore file transfer couldn't be completed (except for the first file). When NOT reproducing the bug, DUT correctly receives prompts for all subsequent file transfers via bluetooth and files were properly transferred.

Bug reproduces in:
Device: Flame 2.2 Master (KK, shallow flash, 319MB mem)
Build ID: 20141224153934
Gaia: ab41c35eed35404b632a4841714b81b56364ba32
Gecko: 2acb12da9813
Version: 37.0a1 (2.2 Master)
Firmware Version: v188-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0

Bug no longer reproduces in:
Device: Flame 2.2 Master (KK, shallow flash, 319MB mem)
Build ID: 20141229071436
Gaia: ea413f7cdec44db0e241c0820e0aca2daeac436c
Gecko: a4a5d4fb5e2e
Version: 37.0a1 (2.2)
Firmware Version: v188-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0

----------

On Flame 2.1/2.0, this particular STR cannot be completed. DUT cannot receive a file transfer prompt without pairing with the remote device first. (As opposed to 2.2, where DUT can receive files as long as its bluetooth status is set to 'visible to all'; two devices don't need to be paired up first.)

Device: Flame 2.1 (KK, shallow flash, 319MB mem)
Build ID: 20141226091635
Gaia: 73be51f998031f06db0cd660c0e388fa621c9f4c
Gecko: ea426e47bfc4
Version: 34.0 (2.1)
Firmware Version: v188-1
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

Device: Flame 2.0 (KK, shallow flash, 319MB mem)
Build ID: 20141229091633
Gaia: 01c32dcdc08b3c8fc8b3082870439fa2c1089f4f
Gecko: b4ea79d5c1b2
Version: 32.0 (2.0)
Firmware Version: v188-1
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

---

Note setting tracking flag on 2.1/2.0 because either it's a bug in 2.2 or it's a new feature in 2.2 to be able to receive files without pairing up.

Comment 4

[Pi Wei Cheng [:piwei] (inactive)]

typo on the last sentence above, *NOT* setting tracking flag.

Comment 5

[[e-mail], [e-mail]]

I would like to nominate the issue to be a blocker. Because it makes the file transfer broken in case of receiving files. We still have a work around solution to show 'unknown device' name instead of waiting API reaching the remote device name.

Need info Jamin for the work around solution.

Comment 6

[Ben Tian (inactive)]

(In reply to Pi Wei Cheng [:piwei] from comment #3)
> Note setting tracking flag on 2.1/2.0 because either it's a bug in 2.2 or
> it's a new feature in 2.2 to be able to receive files without pairing up.

It's a new feature since 2.2 per bug 1066461 comment 14.

Comment 7

[Ben Tian (inactive)]

Cannot reproduce on the latest m-c build.

Device: Flame 2.2 Master (KK, shallow flash, 319MB mem)
Build ID: 20150105160215
Gaia: 4ceeff19086b2a2955f044ad923dcfa63a293de3
Gecko: 912036eeb024
Version: 37.0a1 (2.2)
Firmware Version: v188

Comment 8

[[e-mail], [e-mail]]

I'm not able to reproduce the issue today with following build version.

Gaia-Rev        d53fd8a096923e4b7ad5c8566da44a81d8187034
Gecko-Rev       https://hg.mozilla.org/mozilla-central/rev/636498d041b5
Build-ID        20150104151841
Version         37.0a1
Device-Name     flame
FW-Release      4.4.2
FW-Incremental  eng.cltbld.20150104.190103
FW-Date         Sun Jan  4 19:01:14 EST 2015
Bootloader      L1TC10011800

If someone can reproduce it, feel free to reopen it. Thanks.