Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crash with _CFAssertMismatchedTypeID when browsing for peers stops #12

Closed
insidegui opened this issue Jul 7, 2021 · 0 comments
Closed
Labels
bug Something isn't working

Comments

@insidegui
Copy link
Owner

insidegui commented Jul 7, 2021

This crash manifests itself when stop() is called on MultipeerTransceiver during the lifetime of the application. It usually takes multiple starts/stops for the crash to be reproduced. I can reproduce it reliably in macOS 11.4 and 12 beta 2.

Searching for this assertion produced this thread in the Apple Developer Forums, which seems to indicate that it's some problem with the internal implementation of MultipeerConnectivity, not something caused by improper use of the API.

In my testing, it seems to only occur when browsing is stopped and restarted multiple times with the same instance of MCNearbyServiceBrowser. If the browser is destroyed and reconstructed, it doesn't occur. Therefore, the workaround will be implemented in MultipeerKit so that it destroys the browser when stop() is called, and creates a new one if resume() is called after that.

@insidegui insidegui added the bug Something isn't working label Jul 7, 2021
insidegui added a commit that referenced this issue Jul 7, 2021
Recreate browser and advertiser between discovery sessions (Closes #12)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant