koobas.hobune.stream
iOS IL2CPP Networking Issues Unity 5.0.x
Just wondering if anyone is running into(or has run into) similar issue where Unity networking features don't seem to be working on iOS devices when built from Unity 5.0.x with IL2CPP.
Build Settings Configuration (Current Unity Version: 5.0.2p3)
Scripting Backend: IL2CPP
Target Device: iPhone + iPad
Target Solution: Native
Architecture: Universal
Currently, the networking features in my game are heavily reliant on RPCs. Using the above build settings, I am able to generate and build to an iOS device through Xcode just fine. However, at the point in the game where players need to login (i.e. start using RPCs) the app seems to stop working properly. Judging from the output in the console window in Xcode (I threw in some debug logs before and after the RPC calls just to make sure it was indeed being called) and logging on my server, none of the RPCs sent from the app seem to be reaching the server. Nonetheless, The server does register the app is connected though. There also isn't any error messages being thrown at any point regarding failed RPCs in Xcode's console window. =(
From my research regarding this issue, the majority of posts similar to this problem seem to be regarding Unity 4.6.x. Ideally, I hope it doesn't come the point where I would have to downgrade my project to Unity 4.6.x. Moreover, from the patch notes on Unity's site regarding the 5.0.2p3 patch, there seem to be some fixes regarding RPCs. Unfortunately, as described above, this didn't seem to solve the issue.
All in all, if anyone has had any success building iOS apps with Unity 5.0.x with IL2CPP, any help or suggestions would be very much appreciated!
Cheers
NOTE: When building the project using the Mono scripting backend everything works perfectly fine. But since Mono doesn't support ARM64, I need to get IL2CPP working.
Seconding this. Obviously 64-bit iOS support had to come out in a big hurry, but I wish there was some clue as to when Networking features will be restored. I hope it's top priority because clients don't really appreciate it when your client-server app suddenly can't be updated anymore.
I seem to be running into the exact same problem as described. We're hoping the next Unity Patch will fix this, but it sucks having to wait in no man's land. This seems to be a pretty big issue.
If possible, can anyone involved in this conversation submit a bug report with a 5.0 project that we can use to reproduce and correct the errors? I don't think there is anything in the upco$$anonymous$$g 5.0.2p4 patch release which will fix networking problems specifically. At the moment, we're only aware of one $$anonymous$$or networking bug in 5.0, which does not look the same as this one. Thanks.
Thanks. I have submitted a bug report with a simple dummy project attached. reference
The patch 5.0.3p2 worked very well for me. Thanks Unity team for fixing this!
Small consolation, but I just downgraded our project to 4.6.5p4, and RPC calls appear to work on build. There also weren't really (in our case) any issues with the downgrade, except for the loss of the UnityEngine.iOS namespace.
What this means, I hope, is that the fix for 5 is just around the corner. Perhaps duplicate your project folder and try to downgrade the copy specifically for building out to Xcode? At least then you can just bury it in shame if things go horribly wrong.
Thanks the heads up $$anonymous$$ultivarious01, I guess downgrading would be the only option for now.
My Issue Solved...........!
**Using Unity:**Unity 5.1.1.p1
unity settings
Stripping Level :None
Script Backend:IL2CPP
Target Device: iPhone + iPad
Architecture: Universal
