Search Issue Tracker
Not Reproducible
Fixed in 2018.3.X, 2019.1.X
Votes
1
Found in
2018.3.6f1
2018.3.8f1
2019.1.0b1
2019.2.0a2
Issue ID
1134919
Regression
Yes
Google Play Console APK Pre-Launch report contains IL2CPP related crashes
Steps to reproduce:
1. Open user attached project
2. Build Android apk
3. Upload it into Google Play as an Alpha or Beta release
4. After waiting for prelaunch report to be generated, look at the crashes
Reproducible with: 2019.2.0a8, 2019.1.0b6, 2018.3.8f1
Regressed in: 2019.2.0a2, 2019.1.0b1, 2018.3.6f1
Comments (19)
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
- Frame Debugger is not disabled when switching Scenes if the Frame Debugger window is not open during the transition
- Standalone Profiler Targets another Project if a Standalone Profiler was launched in it before when switching between Edit or Play Mode Targets
- Crash on ForwardRenderLoopJob when opening a specific project
- [Android] Memory leak and eventual crash on Snapdragon 8 Gen 1+ devices when a Clear Pass is executed after Framebuffer Fetch
- PhysicsRaycaster ray length is incorrect when casting from rotated Camera
MartinPegg
May 10, 2019 08:14
You can actually fix this yourselves by modifying 2 files:
Unity.app/Contents/il2cpp/libil2cpp/os/Android/Image.cpp
Change the Initialize function to this:
void Initialize()
{
#if IL2CPP_PLATFORM_SUPPORTS_CUSTOM_SECTIONS
InitializeManagedSection();
#endif
}
Unity.app/Contents/il2cpp/libil2cpp/os/c-api/il2cpp-config-platforms.h
Comment out lines 74 and 75 (depending on version):
//#define IL2CPP_PLATFORM_SUPPORTS_CUSTOM_SECTIONS 1
//#define IL2CPP_METHOD_ATTR __attribute__((section ("__TEXT," IL2CPP_BINARY_SECTION_NAME ",regular,pure_instructions")))
Hope this helps...
trooper
Apr 12, 2019 08:20
Is this being fixed in 2018?
SampaioDias
Mar 18, 2019 14:08
PLEASE, fix this for 2018.3. Terrible regression.