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

Android 7.0 cannot send data #46

Closed
h124551753 opened this issue Apr 22, 2017 · 5 comments
Closed

Android 7.0 cannot send data #46

h124551753 opened this issue Apr 22, 2017 · 5 comments
Labels

Comments

@h124551753
Copy link

Android 7.0 cannot send data with IP both "255.255.255.255" and other IPs

@jsdario
Copy link

jsdario commented May 12, 2017

Seems it does not work on multicast, either.

Any help / insights? Is there a workaround I could use?

@flomair
Copy link

flomair commented Jul 18, 2017

This issue is fixed by https://github.com/netbeast/react-native-udp. @jsdario maybe you can submit a pull request

@jsdario
Copy link

jsdario commented Jul 18, 2017

I believe in Netbeast we are currently using both, netbeast/react-native-udp and this project @v2.0.0 indistinguishbly.

Actually we found weird behaviour only when calling setBroadcast in Android 7 devices, which aparently is not necessary for it to work, only in Android, so in many ocasions you'll find code like the following:

if (Platform.OS !== 'android') {
  socket.setBroadcast(true)
}

This is however counter intuitive and, from my vary basic Linux knowledge, simply wrong. However it did the trick and sockets close normally. It is a huge workaround but I did not research further into the Java side to prove that actually our fork solves it. Initially it just changes how async threads are allocated and applies some styling.

@ericmillsio
Copy link

Had this issue. The netbeast updates @flomair mentioned does work well! It's also still backwards compatible at the least back to Android 5.

@github-actions
Copy link

github-actions bot commented May 8, 2020

Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community attention? This issue may be closed if no further activity occurs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants