NotSupportedException get_HasShutdownStarted - "This icall is not supported by il2cpp

Hi,

I'm getting the following exception from my iOS App:


NotSupportedException: /Users/builduser/buildslave/unity/build/External/il2cpp/il2cpp/libil2cpp/icalls/mscorlib/System/Environment.cpp(166) : Unsupported internal call for IL2CPP:Environment::get_HasShutdownStarted - "This icall is not supported by il2cpp

This is the C# stackstrace that I have:

System.Threading.ThreadPoolWorkQueueThreadLocals.Finalize () (at <00000000000000000000000000000000>:0)
System.UnhandledExceptionEventHandler:Invoke(Object, UnhandledExceptionEventArgs)

Anything I can do?

 

Ok, Thanks!

 

I am still getting the same error in Unity 2017.2.0f2 on iPad Air 2 build from Xcode.

NotSupportedException: /Users/builduser/buildslave/unity/build/External/il2cpp/il2cpp/libil2cpp/icalls/mscorlib/System/Environment.cpp(166) : Unsupported internal call for IL2CPP:Environment::get_HasShutdownStarted - "This icall is not supported by il2cpp."\
at System.Threading.ThreadPoolWorkQueueThreadLocals.Finalize () [0x00000] in <00000000000000000000000000000000>:0 \
UnityEngine.UnhandledExceptionHandlerrintException(String, Exception)\
UnityEngine.UnhandledExceptionHandler:HandleUnhandledException(Object, UnhandledExceptionEventArgs)\
System.UnhandledExceptionEventHandler:Invoke(Object, UnhandledExceptionEventArgs)\
\
(Filename: currently not available on il2cpp Line: -1)\

 

Hi,

I've updated to version 2017.2.0p2 and the above error is gone.
However, now I'm getting the following exception and my app crash

/Users/builduser/buildslave/unity/build/External/il2cpp/il2cpp/libil2cpp/icalls/mscorlib/System/AppDomain.cpp(189) : Unsupported internal call for IL2CPP:AppDomain::InternalIsFinalizingForUnload - "This icall is not supported by il2cpp"

Is this a known issue? Can I do something to solve it?

 

OK, is there something that we can do to workaround this? Or maybe we're doing something wrong? When does the above method get called?

We waited for the mentioned patch, really bad, and now we're just getting the same behavior but with different exception...
Now our iOS app crashes all the time, due to this missing implementation...

 

Switching back to the old scripting runtime is not an option for us...

 

Ok, I'll try that, thanks.

 

Can you be more specific about which patch release?

 

NotSupportedException: /Users/builduser/buildslave/unity/build/External/il2cpp/il2cpp/libil2cpp/icalls/mscorlib/System/Environment.cpp(166) : Unsupported internal call for IL2CPP:Environment::get_HasShutdownStarted - "This icall is not supported by il2cpp

Getting this in 2017.2.0p3. Did you not say it was fixed in p2?

 

Alright, thanks

 

Hi. Is there any version/patch of Unity which does not have these bugs today?

 

2017.3p1 still the same error. :-(

 

Hi,
I'm still getting this

Non-fatal Exception: /Users/builduser/buildslave/unity/build/External/il2cpp/il2cpp/libil2cpp/icalls/mscorlib/System/AppDomain.cpp(189)
Unsupported internal call for IL2CPP:AppDomain::InternalIsFinalizingForUnload - "This icall is not supported by il2cpp."

/Users/builduser/buildslave/unity/build/External/il2cpp/il2cpp/libil2cpp/icalls/mscorlib/System/AppDomain.cpp(189)
0 (Missing) 0x0 Finalize (System.Threading.ThreadPoolWorkQueueThreadLocals)


This is serious problem for us can you please provide some details. Is this somehow connecting with exception handling or maybe UdpClient?

Version is 2017.3.0f3

Also is exception handling on iOS is going to be stable any time soon?
System libraries like UdpClient rely on Exceptions, would we get more stable results if we switch to Berkley sockets and native c++ implementation?

 

I am seeing this as well. My team is using Unity 5.6.3p4 and would greatly prefer to avoid updating to 2017.2 in the immediate future. This was not happening until we switched to the 4.6 version of .NET. We cannot switch back since our UWP app must support Xbox Live to be shipped on the Xbox, and the XboxServices plugin provided specifically requires building against .NET 4.6.

Is there any way we can work around this problem? Modifying the IL2CPP build's contents is problematic for our automated build process.

This may not be the best venue, but I'd also like to ask a broader question. Did anyone at Unity actually test building a UWP IL2CPP app that authenticates to Xbox Live and uses their SSO (both required for Xbox submission) and confirm that the app could build, run, and potentially be accepted by Microsoft? I ask because I am several weeks in to trying to do this and this is not the first blocking problem I've encountered in doing so. It would be great if Unity could test doing that, fix the problems that come up, and basically provide an engine that produces a shippable game for this console platform.

Here are some other, unrelated changes that might have made this process easier:
* Provide a way to sign in and request SSO tokens for Xbox Live without having to upgrade to .NET 4.6 at all, since doing so has led to us encountering multiple land mines.
* Provide a way for Unity to merge the XboxServices.config into the visual studio project, instead of this being a(nother?) manual step that must be done in each build
* Fix the fact that any attempt to use the class System.Net.ServicePointManager leads to runtime errors ("The 'ExeConfigFilename' argument cannot be null.") - or at least let me know how on earth I could hack around this problem (this was another .NET 4.6 land mine) (I just reported it as a bug, #1008073)

 

What is that step exactly? Is it only for UWP titles or ERA too? I can't find anything for xbox apps on how to do that. I tried copying the file everywhere and I still get errors about it being missing.

 

See the second troubleshooting point here: https://docs.microsoft.com/en-us/wi...th-partner/partner-add-xbox-live-to-unity-uwp

And though it's for non-Unity games, there are more details on this page, see step 6: https://docs.microsoft.com/en-us/wi...artner/get-started-with-visual-studio-and-uwp

 

Yeah but that's for UWP. I'm building for native xbox with IL2CPP, if I open the UserAssembly_2015.sln, it doesn't compile. So there's no point in changing anything in there. Anyway, just copying the file manually to the build folder seems to work.

 

This icall is not supported by il2cpp

I am facing this issue on iOS now but works fine on Android and unity editor, using unity version 2019.4.19f1