socket.io-unity icon indicating copy to clipboard operation
socket.io-unity copied to clipboard

Client connects but does not emit data.

Open zoecarver opened this issue 8 years ago • 5 comments

I love this module and have not stopped using it for the last 24 hours. However I am running into a problem. I opened the demo project and when I run it in the unity editor it works wonderfully. But when I build it and then run it in the unity editor simultaneously, The one in the unity editor emits properly and the one that is not in the unity editor connects (a user connected, user id: X) but does not emit anything. Do you know why this is? Is there a fix?

I am running OSX.

zoecarver avatar Jul 18 '17 19:07 zoecarver

In my situation of building it into .apk for android, you have to make sure the configuration of network is ".NET 2.0" instead of ".NET 2.0 Subnet"! Hoping this will help you because I'm also suffer from this problrm for days.

sonysatiou1 avatar Jul 19 '17 17:07 sonysatiou1

Oh~And thank floatinghotpot for this awesome package, too!

sonysatiou1 avatar Jul 19 '17 18:07 sonysatiou1

I have updated to unity beta which should fix the building problem. But now it does not emit anything (except for connect) when I run it in the editor either. For some reason this seams really spotty. I do not have the faintest idea why it is not working.

I would love to hear from someone that got this working what the trick is, because I think this is a great package and I really want to make it work.

zoecarver avatar Jul 19 '17 21:07 zoecarver

I take back what I said. Updating to unity beta does not solve the problem. It must not be a .net issue.

zoecarver avatar Jul 20 '17 19:07 zoecarver

Same problem here. Can't debug out where the problem is.

mihonninja avatar Jan 06 '18 18:01 mihonninja