playMaker

Author Topic: unity 2019.3 IL2CPP build error[SOLVED]  (Read 4320 times)

Tonymed

  • Playmaker Newbie
  • *
  • Posts: 2
unity 2019.3 IL2CPP build error[SOLVED]
« on: August 17, 2019, 04:53:25 AM »
Hello , i got error when building android with il2cpp on unity 2019.3 all alpha versions :
stdout:

Building libil2cpp.so with AndroidToolChain

Output directory: C:\Users\Fhima\Documents\New Unity Project (2)\Temp\StagingArea\assets\bin\Data\Native\armeabi-v7a

Cache directory: C:\Users\Fhima\Documents\New Unity Project (2)\Library\il2cpp_android_armeabi-v7a\il2cpp_cache

il2cpp.exe didn't catch exception: Unity.IL2CPP.Building.BuilderFailedException: C:\Users\Fhima\Documents\New Unity Project (2)\Temp\StagingArea\Il2Cpp\il2cppOutput\PlayMaker2.cpp:31093:14: error: no matching function for call to 'Object_op_Equality_mBC2401774F3BE33E8CF6F0A8148E66C95D6CFF1C'

bool L_1 = Object_op_Equality_mBC2401774F3BE33E8CF6F0A8148E66C95D6CFF1C(L_0, (Object_tAE11E5E46CD5C37C9F3E8950C00CD8B45666A2D0 *)NULL, /*hidden argument*/NULL);

^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

C:\Users\Fhima\Documents\New Unity Project (2)\Temp\StagingArea\Il2Cpp\il2cppOutput\PlayMaker2.cpp:13535:41: note: candidate function not viable: no known conversion from 'GUITexture_t1679093D89FD7E758DB296145046F8BB10DB7E51 *' to 'Object_tAE11E5E46CD5C37C9F3E8950C00CD8B45666A2D0 *' for 1st argument

IL2CPP_EXTERN_C IL2CPP_METHOD_ATTR bool Object_op_Equality_mBC2401774F3BE33E8CF6F0A8148E66C95D6CFF1C (Object_tAE11E5E46CD5C37C9F3E8950C00CD8B45666A2D0 * ___x0, Object_tAE11E5E46CD5C37C9F3E8950C00CD8B45666A2D0 * ___y1, const RuntimeMethod* method);

^

C:\Users\Fhima\Documents\New Unity Project (2)\Temp\StagingArea\Il2Cpp\il2cppOutput\PlayMaker2.cpp:31122:14: error: no matching function for call to 'Object_op_Equality_mBC2401774F3BE33E8CF6F0A8148E66C95D6CFF1C'

bool L_1 = Object_op_Equality_mBC2401774F3BE33E8CF6F0A8148E66C95D6CFF1C(L_0, (Object_tAE11E5E46CD5C37C9F3E8950C00CD8B45666A2D0 *)NULL, /*hidden argument*/NULL);

^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

C:\Users\Fhima\Documents\New Unity Project (2)\Temp\StagingArea\Il2Cpp\il2cppOutput\PlayMaker2.cpp:13535:41: note: candidate function not viable: no known conversion from 'GUIText_t8C9642311EE384C7674771DDF6AB9F222CA1AE1D *' to 'Object_tAE11E5E46CD5C37C9F3E8950C00CD8B45666A2D0 *' for 1st argument

IL2CPP_EXTERN_C IL2CPP_METHOD_ATTR bool Object_op_Equality_mBC2401774F3BE33E8CF6F0A8148E66C95D6CFF1C (Object_tAE11E5E46CD5C37C9F3E8950C00CD8B45666A2D0 * ___x0, Object_tAE11E5E46CD5C37C9F3E8950C00CD8B45666A2D0 * ___y1, const RuntimeMethod* method);
_____
I am using the last version of Playmaker it was working fin with unity 2018 but now i cant downgrade the unity version to 2018.x , this will break UI and terrain data :( , any idea to fix this please ?
« Last Edit: March 25, 2020, 05:16:34 AM by jeanfabre »

djaydino

  • Administrator
  • Hero Member
  • *****
  • Posts: 7615
    • jinxtergames
Re: unity 2019.3 IL2CPP build error
« Reply #1 on: August 18, 2019, 08:13:17 AM »
Hi.
Do you use any Get/Set properties actions?

If so, did you use Linker Wizard?

Tonymed

  • Playmaker Newbie
  • *
  • Posts: 2
Re: unity 2019.3 IL2CPP build error
« Reply #2 on: August 19, 2019, 09:55:56 AM »
Hello, yes i am using get/set prop and i am not using linker wizard , btw i already posted this error in the unity's forum and Alex chouls solved this bug in 1 day , i want to thank him again :D

djaydino

  • Administrator
  • Hero Member
  • *****
  • Posts: 7615
    • jinxtergames
Re: unity 2019.3 IL2CPP build error
« Reply #3 on: August 19, 2019, 10:37:11 AM »
Hi.
Nice!

I do recommend tho to use Linker wizard or look for dedicated actions.

TLN_1

  • Playmaker Newbie
  • *
  • Posts: 2
Re: unity 2019.3 IL2CPP build error
« Reply #4 on: March 24, 2020, 05:20:15 AM »
What was the solution to this? I can't find it on the Unity forum. Do you have a link or a solution?

TLN_1

  • Playmaker Newbie
  • *
  • Posts: 2
Re: unity 2019.3 IL2CPP build error
« Reply #5 on: March 24, 2020, 06:49:34 AM »
If anyone else comes across this Issue, I was on Unity 2019.3.5 and by updating playmaker to the 1.9.0 version seemed to solve that