An endpoint that never goes away (Low-Level)

[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

[bourdakos1]

@RemiNVG can you take a look at this?

[Droppix]

Sorry...I don't understand??

[yerzhant]

I guess the same is here

[yerzhant]

Yep, looks like some caching issue.

[yerzhant]

May it be connected somehow with the latest update of Google Play Services to 24.23.35? As before that I didn't observe such an issue.

[yerzhant]

Actually I do not know whether GPS has been updated or not but update came from Samsung:
One UI version: 6.1
Android version: 14
Versions: G99.../../...
Size: 2157.27 MB
Security fix level: 1st may of 2024

[yerzhant]

@bourdakos1 @RemiNVG could you please advise us what may be cause of that?

[yerzhant]

And as the project isn't open sourced let us know the reason behind this:

E/NearByService(31054): com.google.android.gms.common.api.ApiException: 13: ERROR
E/NearByService(31054): 	at com.google.android.gms.internal.nearby.zzdo.setFailedResult(com.google.android.gms:play-services-nearby@@19.2.0:1)
E/NearByService(31054): 	at com.google.android.gms.internal.nearby.zzce.zzb(com.google.android.gms:play-services-nearby@@19.2.0:4)
E/NearByService(31054): 	at com.google.android.gms.internal.nearby.zzfr.zza(com.google.android.gms:play-services-nearby@@19.2.0:3)
E/NearByService(31054): 	at com.google.android.gms.internal.nearby.zzb.onTransact(com.google.android.gms:play-services-nearby@@19.2.0:3)
E/NearByService(31054): 	at android.os.Binder.execTransactInternal(Binder.java:1380)
E/NearByService(31054): 	at android.os.Binder.execTransact(Binder.java:1311)

[yerzhant]

On trying to discover a second time one can see in logs these errors:

2024-06-30 19:56:52.776 15057-7489  NearbyMediums           com.google.android.gms.persistent    E  MEDIUM_ERROR [SYSTEM][WIFI_LAN][CONNECT][ESTABLISH_CONNECTION_FAILED][UNKNOWN], service-id=com.example.nbs
2024-06-30 19:56:52.797 15057-7489  NearbyMediums           com.google.android.gms.persistent    E  MEDIUM_ERROR [SYSTEM][WIFI_LAN][CONNECT][ESTABLISH_CONNECTION_FAILED][UNKNOWN], service-id=com.example.nbs
2024-06-30 19:56:52.807 15057-7489  NearbyMediums           com.google.android.gms.persistent    E  MEDIUM_ERROR [SYSTEM][WIFI_LAN][CONNECT][ESTABLISH_CONNECTION_FAILED][UNKNOWN], service-id=com.example.nbs