Functional wrapper for Apple's MultipeerConnectivity framework.

Hi there! Spent a lot of time on trying to resolve the problem, the code is actually here: https://gist.github.com/Luccifer/5e588502992124a1b0ec184361bfcd4c

Log: https://gist.github.com/Luccifer/60e55e17507012793c8b6d412bf5e9f4

Help please, I googled it and people usually turning off the encryption, but this didn't help, I have already tried to change it in sources of Pod..

Been using this library and it works fine. However, I am getting intermittent errors that cause it to crash. Below is a sample of the crash report

6 PeerConnectivity 0x00000001013449d8 0x101338000 + 51672 7 PeerConnectivity 0x000000010134ab1c 0x101338000 + 76572 8 PeerConnectivity 0x000000010134b4b4 0x101338000 + 79028 9 PeerConnectivity 0x0000000101356e48 0x101338000 + 126536 10 PeerConnectivity 0x000000010134b2c4 0x101338000 + 78532 11 PeerConnectivity 0x0000000101343164 0x101338000 + 45412 12 PeerConnectivity 0x000000010134ab1c 0x101338000 + 76572 13 PeerConnectivity 0x000000010134b4b4 0x101338000 + 79028 14 PeerConnectivity 0x0000000101353a2c 0x101338000 + 113196 15 PeerConnectivity 0x0000000101353010 0x101338000 + 110608 16 MultipeerConnectivity 0x00000001a1bdf02c __58-[MCSession syncHandleNetworkEvent:pid:freeEventWhenDone:]_block_invoke.630 + 144

i can't isolate where in the code it's happening. i've seen similar postings like this. seemed to be around the MCSession synchandleNetworkEvent call

any insight would really help.

How do you call the viewcontroller for searching advertisers with the inviteOnly option? it's kind of unclear to me. Just setting the connection type to inviteOnly and then writing pcm.start does not seem to change anything :(

Hi @rchatham Just want to make sure if Pod install v0.5.3 supports Swift 3.0 already?

By looking at Github repo, it seems yes, but I still got warning messages after installation. I've followed the instruction to install PeerConnectivity by Pod pod 'PeerConnectivity', '~> 0.5.3'

Thanks for helping out!

Description

status: last testing stage

This might looks like a lots of change but the pull-request include differents things:

• new files and update to projects / settings (.gitignore, pod spec, example project, playground)
• some reoganisation of extensions into new files or re-order of properties of functions
• update multiple types with news attributes for feature like 'security', 'discoveryInfo' & 'connectionMode'
• update of the EventProducers for Sessions, Advertiser & Browser

Sessions - MCSession delegate & event producer

PeerSession can represent either a advertiser session (local-service) or a connection to a 'distant-service' invited through PeerBrowser

thus we now have access to the following attributes:

• sessionPeer - indicate this is a distance-service-session and represent the peer advertising that servicer
• isLocalServiceSession - computed property that check peer against peerSession
• isDistantServiceSession - computed property too

PeerSession can now take security parameter at init allowing to configurer the kind of security to use on the MCSession

Advertisers - MCNearbyServiceAdvertiser delegate & event producer

Advertiser didn't change too much, we can now use discoverInfo at init which couple with Peer.context allow better introspection of services and peer.

Before we used poorly named service to differentiate environment or restaurants, now we can name our services simply and use discoveryInfo to filter matching services.

Browser - MCNearbyServiceBrowser delegate & event producer

Main change to browser is the new sessionFactory logic introduced. The browser will use the sessions attribute when uses as a single slave connection, but will create new session through the factory if configured as node browser.

This will allow to create new session for each services we're connecting to.

Description

Added additional safety on 'foundPeer' modification for on sessionObserver event. This re-use the already available mutex from PeerConnectionManager preventing multiple thread from updating internal data at once.

Should fix the following firebase crash:

Firebase #5cdc6448f8b88c296302a7e7

Description

Adds new Invitation.Status type which help identify in which state in the invitation (and thus peer) is.

Possible cases are unknown, pending, failed and inconsistent in order.

Best case scenario a invitation would see the following status:

unknown -> pending -> invitation removed

In case the invitation fail the following status would happen:

unknown -> pending -> failed -> pending -> failed -> pending -> invitation removed

in worst case scenario the invitation would fail quickly:

unknown -> inconsistent -> inconsistent -> still failing = ignoring peer

Description

Adds 'Invitation' type directly managed by PeerBrowser, once a user called Invite through PeerManager the PeerBrowser will check it's invitation array.

This allow multiple fixes and security in the connections business logics:

• It prevent a user to invite the same peer multiple times.
• it allow PeerManager to retry invitation when the connection failed
• It also allow to reconnect to peers/advertiser reused by MultipeerConnectivity when a distant PeerAdvertiser has been stop and restart in a small amount of time.

Hello,

There is a problem with the new Xcode. Looks like the library is not signed. Can you please check?

Regards

/private/var/containers/Bundle/Application/22001A3E-3E0A-4863-8356-676F91E560D9/thenotebookdigital.app/Frameworks/PeerConnectivity.framework/PeerConnectivity: code signature in (/private/var/containers/Bundle/Application/22001A3E-3E0A-4863-8356-676F91E560D9/thenotebookdigital.app/Frameworks/PeerConnectivity.framework/PeerConnectivity) not valid for use in process using Library Validation: mapped file has no cdhash, completely unsigned? Code has to be at least ad-hoc signed.