IL2CPP is so frustrating.

Edit: all my problems have been resolved and I take back everything I said. Woo Hoo!

 

I think there is a lot of frustration going around at the moment, and we've all had our fair share of bugs, myself, I've had quite a few too.

I try to look at it in the positive light that Unity is going through a transitional phase and trying to make things better for the future of the engine, and with changes comes uncertainty and instability, and we are experiencing that right now.

All we can do is be patient, file bug reports and hope for the best.

 

Thanks man appreciate your words, just sucks when trying to make a living from unity work. Unity is currently getting in the way of my creativity. I love the whole development process except the final publish roadblocks.

 

Bit of a catch 22 really, if they can't upgrade Mono then something has to give sooner or later. With all new software there will be growing pains.. It's not just rumblings of IL2CPP either, there's rumblings of mobile speed issues / bugs / problems with Enlighten etc.

But exactly as @Meltdown says, they are paving the way for the future and if they don't their competition will make them look pretty limp. Some of their competition especially one particular engine has come a hell of a long way over the past two years and it is far more feature complete and advanced, whatever you may actually think of it.

So it's nice, no it's great to see Unity evolving.. Having ease of use with raw grunt is a very enticing proposition, so give it time and reap the rewards ..

 

I too sometimes feel like wanting mono back. But i'm still hopeful that it'll be worth it in the end since the android builds will end up using IL2CPP as well. Less stuff to maintain.

 

My main issue now is Json.net doesn't get processed anymore and I was using it pretty heavily in the application and a few versions ago I was able to build to my phone, now it doesn't even compile.

IL2CPP error for method 'System.Void System.Collections.Generic.IList`1::set_Item(System.Int32,T)' in assembly '/Users/Dustin/Dropbox/Personal/Projects/2014/Warp Drive/WarpDrive/Temp/StagingArea/Data/Managed/Assembly-CSharp.dll'
Additional information: Build a development build for more information. Sequence contains no matching element

 

Yes I filed yesterday. Im willing to do anything on my end to help you guys test.

Case 751015 IL2CPP Build Crashing

 

Thanks Josh I was reading about a possible solution last night, I have been using ASMX and WCF pretty heavily and had non stop issues since Apple forced 64 bit with IL2CPP, Do you recommend I throw them all out the window and do just straight Get/Post requests instead?

 

@Tautvydas Zilys - I second this. @charmandermon - I'm assuming you're the one I've been exchanging emails with about this issue? If not, then you're now the second user that's had these issue. IL2CPP stopped compiling for IL2CPP.

There was originally different IL2CPP compile errors... a load of them that were all pointing to my ReflectionUtils class. As a test to workaround the issue I provided a precompiled DLL for iOS. All of the ReflectionUtils build errors in IL2CPP went away, but then the above error showed up. The above error isn't happening inside of JSON .NET, it's happening with another method, which appears to be originating from simply adding an int to a List<int> or something similar. Looks like a change in IL2CPP bombed out a bunch of compliation with generics.