Skip to content

An endpoint that never goes away (Low-Level) #2472

@Droppix

Description

@Droppix

Project

Nearby Connections

Language

Other

OS Platform

Other

What happened?

I set up a connection between Android (startDiscovery) and Swift (startAdvertising), and then after accepting the connection (iOS side), a connection is established.
When I call stopDiscovery on Android, and "cleanly" stop the process on iOS (stopAdvertising + disconnect), if I restart startDiscovery on the Android side, it still sees the old EndPoint (event -> onEndpointFound), while the connections on the iOS side are all cut...

Impossible to clean up properly, the only solution is to restart the Android device.

What did you expect to happen?

explain above

How can we reproduce it (as minimally and precisely as possible)?

1/ StartDiscovery on Android
2/ StartAdvertising on iOS
3/ Android: Connect to EndPoint (requestConnection)
4/ iOS: AcceptConnection
5/ Android: StopDiscovery
6/ iOS: StopAdvertising
7/ iOS: Disconnect

How often does this bug happen?

Every time

Standalone code to reproduce the issue

...

Relevant log output

No response

Anything else we need to know?

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Priority 2 issue (the default for issues we're likely to work on after P0/P1 issues)platform: androidAn issue with the Android implementationplatform: appleAn issue with the macOS or iOS implementationtype: bugSomething is broken or not working as intended

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions