Connect after stopTransceiving

Open CodeEagle opened this issue 10 years ago • 2 comments

add support for connect not just once I found out that PeerKit just can only run PeerKit.transceive(somename) once, when you run PeerKit.transceive(othername)
after PeerKit.stopTransceiving() PeerKit stop working

Mar 18 '15 04:03 CodeEagle

This is not necessary if you create a new transceiver for start() e.g.

PeerKit.transceiver = Transceiver(displayName: name)
PeerKit.transceive("appname")

Maybe this should be done inside the PeerKit function instead and this might be a cleaner fix.

Mar 22 '15 11:03 alexanderjarvis

multipeer connectivity framework can detect in the background

Jun 09 '15 08:06 xiaomao155