Search Unity

Undefined symbols for architecture armv7: "query_call_back(callback_func_type)"

Discussion in 'Editor & General Support' started by wangxiang_tangiplay, Feb 18, 2020.

  1. wangxiang_tangiplay

    wangxiang_tangiplay

    Joined:
    Nov 2, 2018
    Posts:
    4
    I have upgrade to Unity 2018.4.16c1, after built the ios project, it can't compile in XCode, here is the error log when compile the ios project.

     
  2. WinJay0996

    WinJay0996

    Joined:
    Aug 22, 2019
    Posts:
    2
    I met the same problem. Do you know how to solve it now?
     
  3. wangxiang_tangiplay

    wangxiang_tangiplay

    Joined:
    Nov 2, 2018
    Posts:
    4
    I upgraded to 2018.4.17f1, it is solved.
     
  4. WinJay0996

    WinJay0996

    Joined:
    Aug 22, 2019
    Posts:
    2
  5. ucaslishuo

    ucaslishuo

    Joined:
    Jul 26, 2017
    Posts:
    1
    I met the exact same problem in Unity 2018.4.17f1 with Xcode 11.2.1(11B500)
    Anyone knows how to solve it please ?
    Could it be anything related to my Xcode version (newest is 11.3.1)
    I recently added AdMob SDK to my project. Could it be related ?
     
    sawyerzhu likes this.
  6. sawyerzhu

    sawyerzhu

    Joined:
    Apr 17, 2018
    Posts:
    1
    I have the same problem on Unity 2018.4.19f1 Personal, Xcode 10.1 (10B61).
    I'm recently upgrade my project from Unity 5.6.4 to 2018.4.19f1.
    It's ok to build and run on my device, but if i achieve my iOS project, then the error occurs:

    Undefined symbols for architecture armv7:

    "query_call_back(callback_func_type)", referenced from:

    il2cpp::vm::MetadataCache::Initialize() in libil2cpp.a(External_il2cpp_il2cpp_libil2cpp_vm_6.o)

    il2cpp::vm::MetadataCache::Initialize() in libil2cpp.a(External_il2cpp_il2cpp_libil2cpp_vm_6.o)

    ld: symbol(s) not found for architecture armv7

    clang: error: linker command failed with exit code 1 (use -v to see invocation)

    Anyone can help?
     
  7. Amlovey

    Amlovey

    Joined:
    May 10, 2016
    Posts:
    253
    I have same issue on Unity 2018.4.18f1, I resolved it by switching back to earlier Unity version. I chosen Unity 2018.4.12f1 in my case.
     
  8. Weiwei_Gu

    Weiwei_Gu

    Unity Technologies

    Joined:
    Apr 2, 2019
    Posts:
    1
    This is a bug and it will be fixed in next version of china unity 2018.4.22f1