Closed Bug 789428 Opened 13 years ago Closed 13 years ago

[b2g-bluetooth] the object path of BluetoothDevice is null

Categories

(Core :: DOM: Device Interfaces, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla18

People

(Reporter: gyeh, Assigned: qdot)

Details

Attachments

(1 file)

This bug is caused by patch of bug 756299. For each BluetoothDevice, its mPath should be a combination of adapter's object path and its address. We can't get its object path from DBus and should initialize its value when we get device address.
Damn. My fault having most of the end of development on 756299 be with devices that were already bonded. I'll fix it.
Assignee: nobody → kyle
I pushed path creation back into BluetoothDBusService, as part of any point where we'll pass back a set of properties for Devices. Not like address is ever going to change. Was having a problem finding a way to repro the issue, but I think this should fix it?
Attachment #664230 - Flags: review?(echou)
Comment on attachment 664230 [details] [diff] [review] Patch 1 (v1) - Fix object path setting for BluetoothDevice Review of attachment 664230 [details] [diff] [review]: ----------------------------------------------------------------- Looks good. ::: dom/bluetooth/BluetoothDevice.cpp @@ +62,5 @@ > for (uint32_t i = 0; i < values.Length(); ++i) { > SetPropertyByValue(values[i]); > + if (values[i].name().EqualsLiteral("Path")) { > + // Since this is our signal handler string, set it as we set the property > + // in the object. Odd place to do it, but since this Not even a nit: Unfinished comment?
Attachment #664230 - Flags: review?(echou) → review+
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: