BoxCollider2D not working on link.xml after switch to IL2CPP

So I just made the switch from Mono 2x to IL2CPP due to Apple's requirement of a 64-bit version. My original version was working fine, but now that I'm using a link.xml, BoxCollider2D doesn't seem to work (via Set Property). What I'm trying to accomplish is enabling and disabling the Collider through triggers. The odd thing is that it works fine on Unity, but once it builds to an iOS device, it doesn't. Any help?

Here is my current link.xml:

<linker>
<assembly fullname="UnityEngine">
<type fullname="UnityEngine.SpriteRenderer" preserve="all" />
<type fullname="UnityEngine.BoxCollider2D" preserve="all" />
<type fullname="UnityEngine.Camera" preserve="all" />
<type fullname="UnityEngine.GameObject" preserve="all" />
<type fullname="UnityEngine.Canvas" preserve="all" />
</assembly>
<assembly fullname="UnityEngine.UI">
<type fullname="UnityEngine.UI.Image" preserve="all" />
<type fullname="UnityEngine.UI.Button" preserve="all" />
<type fullname="UnityEngine.UI.Text" preserve="all" />
</assembly>
</linker>

 

@JoshPeterson

I have tried it on both 5.0.1f1 and 5.2.1 with no luck.

Just for a bit more info - I have tried it on both Xcode 6.3.1 and Xcode 7.

 

@JoshPeterson

My project was actually completely finished and in full working condition in Mono until I made the switch to IL2CPP.

Certain triggers are supposed to turn BoxCollider2D off and on, but my player collides with everything (as if the BoxCollider2D is already triggered when it's not supposed to be) when it should be passing through. I am also attempting to enable and disable isTrigger, but that also is not working. Do I need to add anything to my link.xml to allow isTrigger to work on my BoxCollider2D?

It works fine on my Unity, but does not work on my iPad Air or my iPhone 6.

 

I think the main issue lies with the isTrigger. Is there no known fix for that yet? And also, where do I submit the bug report?

 

@JoshPeterson - I have reported the bug with a test scene. The bug number is #732822. I may have forgotten to include the link.xml, but if I did, the one posted here is the one I am currently using. Thanks again for your help!

 

Hi,

We're facing the same thing within the PlayMaker Community

<linker>
<assemblyfullname="UnityEngine">
<typefullname="UnityEngine.BoxCollider2D"preserve="all"/>
</assembly>
</linker>

and that doesn't work when published on IOS, setting the .isTrigger via reflection simply fails without any errors, it just doesn't do anything.

Since there is already a bug being reported, I won't create a new one, but it would be good to address it. I did test it both in Unity 4.7 and Unity 5.3.1 f1

Thanks,

Jean

 

Hi,

indeed that works! Thanks for the hint

Now the problem is going to be the following: how can we know about these combinations? ...

I wrote a wizard that goes over each reflection done ( within PlayMaker ) and output the linker xml content, and so it seems I will have to start creating rules for additional types to preserve... Is there a list somewhere of these types that requires additional preservation entries?

Bye,

Jean

 

Thanks for the infos.

Indeed keeping the whole UnityEngine would defeat the purpose of the linker and optimized build sizes...

So, I have implemented a hardcoded list of types to includes if inherited by the class being reflected. It doesn't cover other similar cases, but at least I'll be able to make updates as we find other classes like BoxCollider2D.


Bye,

Jean

 

Hi Jean-Fabre.... Any chance you can share this list? I am currently trying to figure out the most efficient way to generate a link.xml file for AssetBundles I am loading