Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
Droppix opened this issue Apr 22, 2024 · 2 comments
Open

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

Droppix opened this issue Apr 22, 2024 · 2 comments
Labels
P2 Priority 2 issue (the default for issues we're likely to work on after P0/P1 issues) platform: android An issue with the Android implementation platform: apple An issue with the macOS or iOS implementation type: bug Something is broken or not working as intended

Comments

@Droppix
Copy link

Droppix commented Apr 22, 2024

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

@Droppix Droppix added needs-triage Issue still needs to be assigned, labeled and deduplicated type: bug Something is broken or not working as intended labels Apr 22, 2024
@bourdakos1
Copy link
Collaborator

@RemiNVG can you take a look at this?

@bourdakos1 bourdakos1 added P2 Priority 2 issue (the default for issues we're likely to work on after P0/P1 issues) platform: apple An issue with the macOS or iOS implementation platform: android An issue with the Android implementation and removed needs-triage Issue still needs to be assigned, labeled and deduplicated labels Apr 22, 2024
@Droppix
Copy link
Author

Droppix commented Apr 22, 2024

Sorry...I don't understand??

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P2 Priority 2 issue (the default for issues we're likely to work on after P0/P1 issues) platform: android An issue with the Android implementation platform: apple An issue with the macOS or iOS implementation type: bug Something is broken or not working as intended
Projects
None yet
Development

No branches or pull requests

2 participants