Search Issue Tracker
Fixed in 2018.3.8f1
Fixed in 2018.3.X, 2019.1.X
Votes
2
Found in
2018.3.0a1
2018.3.0f2
2019.1.0a1
2019.2.0a1
Issue ID
1115957
Regression
Yes
[IL2CPP][Mobile] Undefined reference to 'void RegisterUnityClass<AssetImporterLog> when linking a project with Engine Stripping
Repro steps:
1. Open attached project
2. Build on Android
Actual: Build fails with "CommandInvokationFailure: Failed to link 'libunity.so'" error:
stderr[
Temp/StagingArea/strip/armeabi-v7a/UnityClassRegistration.cpp:400: error: undefined reference to 'void RegisterUnityClass<AssetImporterLog>(char const*)'
clang++: error: linker command failed with exit code 1 (use -v to see invocation)
]
Reproducible with: 2018.3.3f1, 2019.1.0a14, 2019.2.0a1
Not reproducible with: 2017.4.18f1
Notes:
- Does repro on Android and iOS with "Strip Engine Code" enabled
- No repro on Mono
- No repro with "Strip Engine Code" turned off
- No repro on Windows/Mac Standalone IL2CPP builds
Fixed in: 2019.2.0a4
Backported to: 2018.3.8f1, 2019.1.0b3
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Long Prefab save times when using Unity 2022.2 and higher
- Console displays error "UnityException: Creating asset at path Assets/Scenes/ .scenetemplate failed." during scene template saving
- "Development Build" watermark is shown in non-development UWP release builds
- Console errors appear when the Inspector is set to Debug and a GameObject is selected
- A script public variable value is not used when set in the Inspector window
Resolution Note (fix version 2018.3.8f1):
Fixed in 2019.2a4