Search Issue Tracker
Won't Fix
Votes
6
Found in
2017.4.0f1
2018.3.0a1
2018.3.11f1
2019.1.0a1
2019.2.0a1
Issue ID
1144147
Regression
No
[Android] [IL2CPP] Android IL2CPP build fails with errors on LWRP project when Mapbox package is installed
How to reproduce:
1. Open attached Unity project
2. Build to Android platform
--build fails with errors:
Failed running D:\Unity\2019.2\2019.2.0a10_f661a28be8b8\Editor\Data\il2cpp/build/il2cpp.exe --convert-to-cpp --emit-null-checks --enable-array-bounds-check --dotnetprofile="unityaot"
Exception: D:\Unity\2019.2\2019.2.0a10_f661a28be8b8\Editor\Data\il2cpp/build/il2cpp.exe did not run properly!
Reproduced with: 2017.4.26f1, 2018.3.13f1, 2019.1.0f2, 2019.2.0a12.
This issue can be reproduced on a newly created project:
1. Create LWRP project
2. Download and import Mapbox 2.0.0 package: https://www.mapbox.com/unity/
3. Install Multiplayer HLAPI 1.0.2 and XR Legacy Input Helpers 2.0.2 packages
4. Switch Platform to Android
5. Set scripting backend to IL2CPP
6. set Minimum API level to Android 7.0 (level 24)
Note: Project builds successfully with mono scripting backend.
Comments (3)
-
AtifatGamy
Sep 21, 2019 15:47
exactly same issue here
-
Tech-Unity3d
May 30, 2019 07:32
Same issue from my side
-
unity_voyTrf45pfG-UQ
May 29, 2019 17:14
https://github.com/mapbox/mapbox-unity-sdk/issues/1315
This is almost the same issue reported on mapbox forum.
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
- "Draw Additional Lights Shadowmap" calls increase when custom MaterialBlockProperty is used
- Crash on _platform_memmove when importing the "Dragon Crashers - URP 2D Sample Project" to a new 2D project
- "Shader is not supported on this GPU" warnings and and shaders are not loading when building the project for non-Chromium browsers
- [iOS][URP] The screen flickers and the "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously
- Shortcut Manager shows empty conflict filter when resolving runtime conflicts involving different contexts
Resolution Note (2019.2.X):
Unity does not support MapBox. All MapBox issues should be addressed with them