iOS il2cpp binary size with 4.6 runtime enabled

Building empty iOS project with 4.6 runtime enabled outputs ~48Mb binary for me.
Running Unity 2017.4.10f1. Engine stripping is enabled. Are there any ways to go below that number?

Check on which Api Compatibility Level you are using. The .NET Standard 2.0 level will be a smaller set of class library code. We recommend using that. Also, you may want to have a look at 2018.2 and 2018.3 beta, as we made significant code size improvements since 2017.4 for the .NET 4.x equivalent scripting runtime.

My sample project is empty project with 1 UnityUI button (so ui sybsystem gets into a build) and 1 script that prints to console upon button click:
Here are my measurements:

2017.4 runtime 3.5 - 28.4m
2017.4 runtime 4.6 - 46.0m

2018.2 runtime 3.5 - 30.6m
2018.2 runtime 4.6 - 47.9m

So 2018.2 makes things event a bit worse, but there is “.NET Standard 2.0” option in it:

2018.2 runtime 4.6 with .NET Standard - 34.4m

2018.3b5 actually makes things worse:

2018.3b5 runtime 4.6 with .NET Standard - 40.7m

Really weird number for 2018.3, probably I need to double check my measurments. In the meantime where I can see mention of Script Runtime optimizations in 2018.3beta release notes?

Yes, unfortunately, the engine code gets bigger over time (which is a different problem from the .NET class library code). Generally, we (the VM team) have been working on making the size for the .NET 4.x Equivalent runtime with similar in size to the .NET 3.5 equivalent runtime on the same version of Unity.

In Unity 2018.3, there should not be much difference between the .NET 4.x and .NET Standard 2.0 Api Compatibility Levels. Note that 2018.3 beta also introduces better managed code stripping options, which can really help with code size. We’re still iterating on how those options are applied, so expect changes to them in the next few beta releases.

I’m not sure what you mean. Can you clarify?

I just wanted to make sure that all optimizations intended for 2018.3 are already in the beta builds. And I actually check that by reviewing release notes here: https://unity3d.com/unity/beta-download but I don’t see anything about stripping options there

Looking forward to new 2018.3 betas

Ok, thanks! We have a few more optimizations for size still in the queue for later 2018.3 beta builds.