Skip to content

BUG: StartScanning with more UUIDs does not working #3

@sebastianhoeck

Description

@sebastianhoeck

Hello,

if found a bug with multiple startScanning / UUIDs.

First: The UUID "51516ED6-830B-485D-B176-0BC1C7B69D3" exists and is on a available beacon next to me.
The Beacon with the uuid C476A05A-5BA5-4D5E-9A37-6E19C8022B15 does also exists, but is not next to me.

If i only write "startScanning('51516ED6-830B-485D-B176-0BC1C7B69D35'..", every thing works fine. The Listener onBeaconsDetected triggered and found the beacon.

If i set the following, also the listener will be triggered and found the beacon with the uuid "51516ED6-830B-485D-B176-0BC1C7B69D35!

Note: The Beacon with the UUID "51516ED6-830B-485D-B176-0BC1C7B69D35" is the first startScanning

startScanning('51516ED6-830B-485D-B176-0BC1C7B69D35', {
            useForegroundService: true,
            useBackgroundScanning: false
});
        
startScanning('C476A05A-5BA5-4D5E-9A37-6E19C8022B15', {
            useForegroundService: true,
            useBackgroundScanning: false
});

If i set set beacon with the uuid "51516ED6-830B-485D-B176-0BC1C7B69D35" at the last, no beacons will be found in the listener.

startScanning('C476A05A-5BA5-4D5E-9A37-6E19C8022B15', {
     useForegroundService: true,
     useBackgroundScanning: false
});

startScanning('51516ED6-830B-485D-B176-0BC1C7B69D35', {
       useForegroundService: true,
        useBackgroundScanning: false
});

In my app i have multiple beacons with different uuids. I have to set "startScanning" in a for-loop. The order of the beacons is everytime different. Is it a bug or am I doing something wrong?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions