-
Notifications
You must be signed in to change notification settings - Fork 159
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
iOS NearbyConnections doesn't work with React Native #2195
Comments
facing same problem |
If I'm not mistaken this is something related to the Flipper, if you disable it on the Podfile you should be able to run the app without any problem. |
I linked the fix in the issue description, you just have to add an #if 0 to one of the files. Disabling flipper did not work for me |
Are you able to open a PR with the fix? I can approve/submit. Otherwise it will probably be about a week until I can take a look at this |
I don't think It's a trivial fix since the change is in the SSL library, not nearby itself. See this PR for how another package fixed it |
It looks like that PR is merged, can we just update the version of the SLL lib we are using? |
Maybe? The linked thread said it might be fixed as of https://boringssl-review.googlesource.com/c/boringssl/+/40405/9#message-0e7e7e16e7576e76dffe8a4be77fe3b1102f4112 (pretty old though, might already be using this). However, they also mentioned that it might be a bug in Folly, and I don't think that's being tracked anywhere... |
Hi @WolfDierdonck , Check the solution I posted here, With this, I was able to get nearby working with React Native. Hope this helps |
Project
Nearby Connections
Language
Swift
OS Platform
Apple
What happened?
When trying to use React Native with Nearby Connections on iOS, the app crashes with an
sdallocx
error inOPENSSL_free
(inside of theBoringSSL-grpc
package) when requesting a connection to another endpoint. Note that discovering/advertising works, it only crashes when requesting a connection.This issue seems very similar to apple/swift-nio-ssl#189 (read the thread for more details, specifically the last few comments). Additionally, the fix used in that package here fixes the issue above.
What did you expect to happen?
No error/crash to happen when requestingConnection
How can we reproduce it (as minimally and precisely as possible)?
How often does this bug happen?
Every time
Standalone code to reproduce the issue
Can't provide any code for this since it's very involved. The steps above should be enough to repro 100% of the time
Relevant log output
No response
Anything else we need to know?
The workaround doesn't seem to introduce any issues so not an urgent issue, just a QOL improvement
The text was updated successfully, but these errors were encountered: