Search Issue Tracker

Fixed

Votes

0

Found in [Package]

1.4.4

Issue ID

UVSB-8

Regression

No

IL2CPP encountered a managed type which it cannot convert ahead-of-time

Package: Visual Scripting

-

Needs More Information - 10 months ago • updated 3 months ago. 1 upvote.

Seems Nasty and affects mobile I2CPP, no debug info or project so will be hard to debug.  1 user has a workaround original user still has issues.

[Original issue link|https://support.ludiq.io/communities/5/topics/3969-il2cpp-encountered-a-managed-type-which-it-cannot-convert-ahead-of-time]
----

Here at work, we are regularly encountering startup errors when building for the IL2CPP-platform. App hangs directly after the unity logo fades, error log shows the following output (only in the device logs):

[Crashlog.txt|https://support.ludiq.io/uploaded/file/21929/5/3156/0a0f1e0b5ca41228ee3c2e9a8cfdafff.txt]

This is usually resolved by reverting some of our recent changes, ie. we had to remove an app-rating plugin once, or the other time we actually had to convert a timeline animation to a regular animator. None of which actually involves any heavily generic or otherwise nested types that should cause this issue.

Now aside from resolving the actual reason, would it be at all possible to instrument this error condition with more information? We'd be interested in the actual type that is causing this problem, so that we will have to spend less time trying to find out what caused the error this time.

(As a side note, we had a very persistent occurance of this error lately, which was only resolved by updating bolt from 1.4.2 to 1.4.4, only to reappear a week afterwards as of today. Also, its happening on both iOS and Android, and we do perform the AotPrebuild often, which is usually the catalyst for the error appearning - meaning it will just stop working after we updated the AotStubs with the prebuild step)
Bolt Version:
1.4.4
Unity Version:
2018.4.2f1
Platform(s):
 
Scripting Backend:
 
.NET Version (API Compatibility Level):

  1. Resolution Note:

    Fixed in 2020.1.14f1

Comments (2)

  1. dave_thrive

    Jan 22, 2021 10:28

    Come on, seriously? The fix requires updating to Unity 2021? Thats not really a fix is it? I have the same issue. Also on 2018 using Bolt 1.4.13

  2. magnusfox

    Oct 14, 2020 09:06

    Did you ever manage to work around this?

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.