4.6 iOS 64-bit beta

The size of our app was 99.5 MB with Unity 4.3.1 (IL2CPP Universal Release), now it's 103 MB with the latest patch! Did other people experience the same issue? Should we wait until the next patch to see if the same issue occurs, or should we work on reducing the size of the textures and sound? We'd love to hear your opinions!

 

@Satoshi Ueda

 

@JoshPeterson Hello, I have run into the same bug as @cojo71 (TypeLoadException) and just submitted bug with case ID 676471. Any news on possible workaround or timetable for a fix? Keep up the good work!

 

I got the same problem.
"WebRequest.Create" casued UnsupportedException.

 

Hello, so from 1 feb 2015 apple wants us to upload binaries with arm64 architecture, does that mean it's a must to use ILC2PP or we won't be able to successfully send the binary? I use reflection.emit which isn't compatible so I can't compile with this architecture.

What are my options here? Can I compile with mono and add arm64 later on Xcode?

 

@JoshPeterson
I'm using 4.6.3p1 version.
I got this error at build time.

Code (CSharp):

1. Undefined symbols for architecture arm64:
2.   "_GetInst_ExtendableMessage_2_GetExtensionCount_m15206_gp_0_0_0_0", referenced from:
3.       GenInst_ExtendableMessage_2_GetExtensionCount_m15206_gp_0_0_0_0_Types in Il2CppGenericInstDefinitions.o
4.   "_ExtendableMessageLite_2_GetExtensionCount_m15168_gp_0_0_0_0", referenced from:
5.       GenInst_ExtendableMessageLite_2_GetExtensionCount_m15168_gp_0_0_0_0_Types in Il2CppGenericInstDefinitions.o
6.      (maybe you meant: _GenInst_ExtendableMessageLite_2_GetExtensionCount_m15168_gp_0_0_0_0)
7. ld: symbol(s) not found for architecture arm64

Is this error also related to code generating by IL2CPP?

 

Reflection.Emit was never allowed on iOS (runtime code gen is forbidden by Apple) no matter what tool or engine used so it does not work with mono either.

 

Jsonnet uses the Reflection.Emit (at least it's using it in some scripts on the source code) and it works with Mono, tested on several iPads and iPhones.

http://forum.unity3d.com/threads/released-json-net-for-unity-3-5-with-aot-support.200336/

 

On some other platforms yes but surely not on iOS, you can even see it yourself by looking at the compiler directives.

 

Oh so we might be lucky and IL2CPP might actually suport jsonnet?

By the way, is System.Cryptography supported? Because I have compiled and it's behaving oddly, different results of MD5 with Mono and ILL2CPP.

 

It's not about luck. JSON.NET already supports AOT platforms which iOS is among few others. The author uses different approach to get the asset work on these platforms. Also @Dustin Horne has been active in this thread to make sure all IL2CPP related issues with it would be resolved (when possible).

However your original issue, Reflection.Emit is not about IL2CPP, JSON.NET or even Unity. It's a restriction set by Apple

 

These MD5 sum/System.Cryptography issues were fixed in 4.6.3p1 - there were some errors in bitwise operators that were causing some issues.

 

Yes, my asset supports il2cpp, though mileage may vary. There are still bugs in il2cpp and some mono features that have not yet been ported over so there may be things that don't yet work, though il2cpp has gotten pretty stable and I'm finally hearing of less issues.

 

I'm using 4.6.3f1, not getting errors but the results aren't the same with IL2CPP and Mono.

 

Yeah, that was the "issue"

 

Building my app with Mono to iOS takes about 30 seconds. With IL2CPP it takes over 30 minutes. The same applies for all our apps at our company that we've tried. (Tried 3 different apps so far).
Anyone else experiencing this? Anyone noticed why this happens? It's quite unbearable and extremely time consuming.
We are using Coherent UI (the new 64 bit version), by the way.

 

I recently benchmarked my build with both methods, and IL2CPP came in at 4.58x slower. They say they are working on this so lets hope they pull off some much needed speed improvements, otherwise it feels like a step backwards.

 

Then it's not fixed?

 

It was fixed in 4.6.3p1. You stated that you were using 4.6.3f1 which is older.

 

Any one else seeing a big slow down in frame rate around rigid body collisions?

 

Holly Molly, your right!

 

It's not 4.58x slower for me. It's way waaaay slower. 30 secs became over 30 mins, closer to 35 actually.

 

Hello, just wondering if you could provide an update for cases 675730 and 670410? Case 670410 I'm no longer getting, but I'm getting the crash bug in 675730 instead so I'm not sure if it is actually fixed or not.

 

I can't reproduce it in 4.6.3p1, as the crash bug occurs. It's possible that the bug is fixed and so revealed the crash bug, but I can't tell yet.

 

Are you using the latest patch 4.3.1p1?

For some reason the first 4.3.1 release was waaay slower for me. It took almost 2 hours (!) to finish the Postprocessing Player phase. Up from 6 min total Unity build time with Mono. Since p1 it's about 20min with IL2CPP, so roughly 4x slower.

 

Same here - IL2CPP is painfully slow, to the point where I keep thinking it's crashed. It takes FOREVER to build out of Unity, and then it takes wayyy longer for Xcode to build. If it's expected to be slower, is it expected to be 100x slower?

 

(NOTE: originally posted the case and this message two weeks ago in the thread named "[Official] The collected il2cpp forum topic." but it seems dead, so trying here)

@JoshPeterson Hi there, Congrats on this awesome new tech! Very excited about it

Our assets "UFPS : Ultimate FPS" and more specifically "Mobile Add-on for UFPS" will build fine to iOS devices using Mono, but will hang using IL2CPP. I have tracked down these issues to our event system, and have submitted my findings in case 673217.

Any assistance with this would be much appreciated since we've had customers waiting to submit to App Store for a couple of weeks and we're starting to feel the heat.

Best,

Cal

 

Thanks @JoshPeterson - i thought I had read this should be better.

I dug into this a bit and found that this weird slowdown was only on one of my oldest prefabs.
It had a mesh collider and flipping convex and smooth sphere colliding fixed it.
I was then able to refactor to a capsule collider and framerate around collisions went back passed normal.

I have since went back thru my mesh colliders and refactored them out.
Everything feels a bit smoother now.

-- edit --
ran a few more tests and it's actually radically better. About 500% better in my case.
Great work!

thanks - appreciate the info.

 

@JoshPeterson Thanks for getting back to me Josh! Thumbs crossed

 

(Case 676103) 4.6.3p2 Facebook broken on FB.FEED, FB.API with a POST
correlating facebook bug https://developers.facebook.com/bugs/1586549588290367/

Can GET from Facebook but not POST

release blocking bug

 

That's too bad, thanks for letting us know!

 

@JoshPeterson
I've already filed a bug here https://fogbugz.unity3d.com/default.asp?675644_hu4stqekap6cgbim
And it's also simple to reproduce this bug, just a few lines of code in http://forum.unity3d.com/threads/4-6-ios-64-bit-beta.290551/page-19#post-1985935

 

@JoshPeterson
And here
http://fogbugz.unity3d.com/default.asp?676327_8ivtqs3b94q7n004

 

Continuously, It seems that below build error was caused by Google Protocol Buffers API.

Code (CSharp):

1. Undefined symbols for architecture arm64:
2.   "_ExtendableMessage_2_GetExtensionCount_m15206_gp_0_0_0_0", referenced from:
3.       GenInst_ExtendableMessage_2_GetExtensionCount_m15206_gp_0_0_0_0_Types in Il2CppGenericInstDefinitions.o
4.      (maybe you meant: _GenInst_ExtendableMessage_2_GetExtensionCount_m15206_gp_0_0_0_0)
5.   "_ExtendableMessageLite_2_GetExtensionCount_m15168_gp_0_0_0_0", referenced from:
6.       GenInst_ExtendableMessageLite_2_GetExtensionCount_m15168_gp_0_0_0_0_Types in Il2CppGenericInstDefinitions.o
7.      (maybe you meant: _GenInst_ExtendableMessageLite_2_GetExtensionCount_m15168_gp_0_0_0_0)
8. ld: symbol(s) not found for architecture arm64

Google Protocol Buffers API

Code (CSharp):

1.  
2. public int GetExtensionCount<TExtension>(GeneratedExtensionBase<IList<TExtension>> extension)
3.     {
4.       return this.extensions.GetRepeatedFieldCount((IFieldDescriptorLite) extension.Descriptor);
5.     }
6.  

Il2CppGenericInstDefinitions.cpp

Code (CSharp):

1. extern Il2CppType ExtendableMessageLite_2_GetExtensionCount_m15168_gp_0_0_0_0;
2. static const Il2CppType* GenInst_ExtendableMessageLite_2_GetExtensionCount_m15168_gp_0_0_0_0_Types[] = { &ExtendableMessageLite_2_GetExtensionCount_m15168_gp_0_0_0_0 };
3. Il2CppGenericInst GenInst_ExtendableMessageLite_2_GetExtensionCount_m15168_gp_0_0_0_0 = { 1, GenInst_ExtendableMessageLite_2_GetExtensionCount_m15168_gp_0_0_0_0_Types };
4.  
5. extern Il2CppType ExtendableMessage_2_GetExtensionCount_m15206_gp_0_0_0_0;
6. static const Il2CppType* GenInst_ExtendableMessage_2_GetExtensionCount_m15206_gp_0_0_0_0_Types[] = { &ExtendableMessage_2_GetExtensionCount_m15206_gp_0_0_0_0 };
7. Il2CppGenericInst GenInst_ExtendableMessage_2_GetExtensionCount_m15206_gp_0_0_0_0 = { 1, GenInst_ExtendableMessage_2_GetExtensionCount_m15206_gp_0_0_0_0_Types };

Please, tell me how I can fix this.

 

Ok, I just thought we were home safe, and that our game worked now... Turns out our ad-hoc builds didn't :-(

I found that DateTime.ToUniversalTime throws System.ArgumentOutOfRangeException: Value 3735262985982536407 is outside the valid range [0,3155378975999999999].

It happens consistently when compiling with the "Release" build configuration.

It happens when the DateTime is the default value, MinValue or MaxValue. The value in the exception is always the same.

The function works normally when compiled with the debug configuration.

At some point it only happened on 32 bit devices but I just tried on a 64 bit device and there it happened too, so not so sure about that.

I filed a bug report with a repro project on this (case 676847)

 

Just saw Unity 5 is out. Does this mean no more patch releases for 4.6.3?
The timing is not the best for us.

 

No, they've stated that they will continue with 4.x updates after 5.0 is released.

 

We have the exact same issue, with both Mono and il2cpp.
Have you found any workaround?

 

Hopefully patch this thursday, but is there a full response to this from Unity dont wish to deter thread of topic, but its really important to have some official information