52832 slaver connected by android app but not find service

This is the bad connect by sniffer packected, you can find it at end of conn_err.pcapng

The peer response to not finding the attribute in the given range seems like a proper response within the discovery service when the attribute in given range is not found. Attribute not found can sometimes be used to know that the end of discovery procedure has been achieved and the app does not need to see to find more attributes after that range.

It seems to me that the service/characteristics are not properly initialized or something else went wrong in the server side. It is still not clear to me why you suspect that the highlighted sniffer packet is wrong?

The peer response to not finding the attribute in the given range seems like a proper response within the discovery service when the attribute in given range is not found. Attribute not found can sometimes be used to know that the end of discovery procedure has been achieved and the app does not need to see to find more attributes after that range.

It seems to me that the service/characteristics are not properly initialized or something else went wrong in the server side. It is still not clear to me why you suspect that the highlighted sniffer packet is wrong?

Thank you for your quick response.

Maybe I didn't express clearly, I mean caught this uncommunicable connection packet.

In this case, I do not disconnect the app, and use nrfconnect to connect, and the service characteristic value can be found.

personally I think that there is a problem on the app side, but we cannot tolerate such a connection, can the slave know this and then disconnect?

Thank you

Sorry for the late response.

You can ofcourse respond to the error that the slave gets and send a disconnect request from the slave.

Sorry for dealing with other things these days.

Thank you for your response.

I know it's ok I meen how can peripheral get the information central find service failure.