Search Issue Tracker

By Design

Votes

0

Found in

6000.0.48f1

6000.1.2f1

6000.2.0a10

6000.3.0a1

Issue ID

UUM-104817

Regression

No

Building the Player takes 25-50% more time in Unity 6 compared to 2022.3 when the IL2CPP scripting backend is selected

-

Reproduction steps:
1. Open the attached “IN-98901” project
2. Switch to the Android Build Platform
3. Make a Clean Build (File > Build Settings, Click the drop down next to Build > Clean Build)
4. Observe the Console

Expected result: Build time in Unity 6 is similar to the time in 2022.3.X
Actual result: The Build in Unity 6 takes 25-50% more time compared to 2022.3.X

Reproducible with: 2023.1.0a5, 6000.0.48f1, 6000.1.2f1, 6000.2.0a10
Not reproducible with: 2022.3.62f1
Couldn’t test with: 2023.1.0a1 (Gradle build error)

Reproducible environments: Windows 10 (by reporter), macOS 15.4.1
Not reproducible environments: No other environments tested

  1. Resolution Note:

    The bug as described can be explained by Unity 6 defaulting to GameActivity (which is a C++ entry point) over Activity in 2022.3. If you switch Unity 6 to use Activity the times and sizes are as reasonably expected (aside from increases as there is more code to compile and we updated the Android NDK in Unity 6).

    As an example, if we set everything to Activity and IL2CPP to "master" we get the following APK sizes and times.

    2022.3.45f1 - 96 seconds - 20.5MB
    6000.0.37f1 (pre NDK update) - 113 seconds - 24.2MB
    6000.0.37f1 (GameActivity) - 78 seconds - 27MB
    6000.0.38f1 (post NDK update) - 87 seconds - 24.8MB
    6000.0.38f1 (GameActivity) - 94 seconds - 27.6MB

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.