I can validate that behavior. Basically following all that there is on the next few pages -> https://developer.apple.com/documentation/wifiaware/building-peer-to-peer-apps after one device become subscriber and the other publisher in a while the same application will want again devices to pair with pin otherwise they will never connect.

I second on this issue. I personally was able to replicate and i need this behavior for my applications.

Hey @sengui the whole idea of Wi-Fi Aware and having it been exposed by Apple is to be able to use it with other platforms. The current way been exposed on their end and the API that exist right now it isn't possible and that's the whole problem we are facing. What is needed from Apple end is to expose the API raw as any other platform does so the developers can take full advantage of it. We are proposing exactly that. As i understand the whole idea of Wi-Fi Aware is to be dynamic so the term peer database doesn't apply and it shouldn't. In case that somehow applies which i don't believe it does that is where the problem lies i suppose. Can you maybe share more information about your own tests with the @DTS Engineer ? That will be helpful As i mentioned it is designed to be dynamic with preserved privacy by the system when discovering. The system shields MAC address and adds opaque handles as well and advertising frequency is changed constantly. The idea is to be ephemeral (short-lived)

Hey @DTS Engineer there isn't a sample code at this stage in the documentation. There is only the documentation explaining how to use Wi-Fi Aware on the Apple platform. Can you provide links to a real sample application to just run and test on our end. Would be happy to reproduce it with your sample code. Right now the documentation looks a bit unfinished with missing states between what you actually see in XCode and the way you need to build a real application. Even if that's the case i have been able to build one on my end and test the flow and the current API.

Hey @DTS Engineer no a sample project in general. The documentation simply can't be called a project. I suppose a sample application project showing iOS<>iOS will be fine too but a complete project which can be used. I am asking for such a project since it would be much easier to replicate issues on Apple end with a project that was already built by Apple. We can easily drop in issues and discuss the exact places. And since you requested that i suppose it's a good time to touch on this.

Hey @DTS Engineer i haven't seen the download button which now seems to appear on top i don't think that was the case before. We can replicate the same issue with that project and came back to you. Let me run few tests with it.

Hey @sengui that's exactly what i am saying too i have been following this very closely and currently as i can see it isn't the case. I hope they resolve this problem soon and open it to everyone.