我有一个非常古老的遗留项目(从 2010 年开始约会)。它的 Crashlytics 套件最后一次更新是在 2013 年的某个地方。
我正在尝试更新它。它不使用 pod,所以我使用了 official Manual update指导。
这些是这里描述的仅有的两个步骤。但是这样做会导致链接器错误:
Undefined symbols for architecture x86_64:
"___gxx_personality_v0", referenced from:
+[CLSDemangleOperation demangleBlockInvokeCppSymbol:] in Crashlytics(CLSDemangleOperation.o)
+[CLSDemangleOperation demangleSwiftSymbol:] in Crashlytics(CLSDemangleOperation.o)
-[CLSDemangleOperation main] in Crashlytics(CLSDemangleOperation.o)
___28-[CLSDemangleOperation main]_block_invoke in Crashlytics(CLSDemangleOperation.o)
Dwarf Exception Unwind Info (__eh_frame) in Crashlytics(CLSDemangleOperation.o)
"vtable for __cxxabiv1::__pointer_type_info", referenced from:
typeinfo for std::exception const* in Crashlytics(CLSException.o)
NOTE: a missing vtable usually means the first non-inline virtual member function has no definition.
"vtable for __cxxabiv1::__vmi_class_type_info", referenced from:
typeinfo for std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > in Crashlytics(CLSException.o)
NOTE: a missing vtable usually means the first non-inline virtual member function has no definition.
"___cxa_begin_catch", referenced from:
CLSTerminateHandler() in Crashlytics(CLSException.o)
___clang_call_terminate in Crashlytics(CLSException.o)
"std::get_terminate()", referenced from:
_CLSExceptionCheckHandlers in Crashlytics(CLSException.o)
"typeinfo for char const*", referenced from:
GCC_except_table1 in Crashlytics(CLSException.o)
"typeinfo for std::bad_alloc", referenced from:
GCC_except_table1 in Crashlytics(CLSException.o)
"typeinfo for std::exception", referenced from:
GCC_except_table1 in Crashlytics(CLSException.o)
typeinfo for std::exception const* in Crashlytics(CLSException.o)
"___cxa_current_exception_type", referenced from:
CLSTerminateHandler() in Crashlytics(CLSException.o)
"___cxa_rethrow", referenced from:
CLSTerminateHandler() in Crashlytics(CLSException.o)
"vtable for __cxxabiv1::__class_type_info", referenced from:
typeinfo for std::__1::__basic_string_common<true> in Crashlytics(CLSException.o)
NOTE: a missing vtable usually means the first non-inline virtual member function has no definition.
"___cxa_end_catch", referenced from:
CLSTerminateHandler() in Crashlytics(CLSException.o)
"___cxa_demangle", referenced from:
+[CLSDemangleOperation demangleCppSymbol:] in Crashlytics(CLSDemangleOperation.o)
"std::terminate()", referenced from:
___clang_call_terminate in Crashlytics(CLSException.o)
"std::set_terminate(void (*)())", referenced from:
_CLSExceptionInitialize in Crashlytics(CLSException.o)
CLSTerminateHandler() in Crashlytics(CLSException.o)
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
我尝试过的事情:
但错误仍然存在。现在,我束手无策。有关如何解决此问题的任何想法?
我想通了。
问题是,前一个人修改了链接器和编译器标志,并从中删除了 $(inherited)
标志,该标志覆盖了 Cocoapods 配置,从而导致无法将主项目与Cocoapods 并因此缺少符号,因为 XCode 在没有链接的情况下找不到符号。
首先我删除了手动 Crashlytics,然后通过 cocoapods 安装了它们。现在它说缺少符号。
解决这个问题:
$(inherited)
添加到调试和发布配置中。 $(inherited)
标志。 Crashlytics 3.8.4 现已启动并运行。
关于ios - Crashlytics 手动更新到 3.8.4 导致链接器错误,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/44887175/
欢迎光临 OStack程序员社区-中国程序员成长平台 (https://ostack.cn/) | Powered by Discuz! X3.4 |