Linker plugin not working when running tests

[joharei]

I have added the linker plugin, but when running iosX64Test or iosSimulatorArm64Test I get the undefined symbols error when building:

Undefined symbols for architecture arm64:
  "_FIRCLSExceptionRecordNSException", referenced from:
      _co_touchlab_crashkios_crashlytics_FIRCLSExceptionRecordNSException_wrapper0 in result.o
  "_OBJC_CLASS_$_FIRCrashlytics", referenced from:
      objc-class-ref in result.o
  "_OBJC_CLASS_$_FIRExceptionModel", referenced from:
      objc-class-ref in result.o
  "_OBJC_CLASS_$_FIRStackFrame", referenced from:
      objc-class-ref in result.o

I have tried similar workarounds like in #46, but I can't get it working.

[jjcoffman]

i have the same issue as above fox x86_64:

▸ Linking MyAppUITests

❌  ld: symbol(s) not found for architecture x86_64



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


    Run script build phase 'Create Symlinks to Header Folders' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'MDFInternationalization' from project 'Pods')
Testing failed:
	Undefined symbol: _FIRCLSExceptionRecordNSException
	Undefined symbol: _OBJC_CLASS_$_FIRCrashlytics
	Undefined symbol: _OBJC_CLASS_$_FIRExceptionModel
	Undefined symbol: _OBJC_CLASS_$_FIRStackFrame
	Linker command failed with exit code 1 (use -v to see invocation)
	Testing cancelled because the build failed.

** TEST FAILED **

[LukasHromadnik]

Hi!
Any updates on this issue?
I cannot run the tests, I can build them though. But still the workaround is not working for tests.

[joharei]

I finally found the right place to apply the linker options so that our tests can run:

tasks.withType<KotlinNativeCompile>().configureEach {
    compilerOptions.freeCompilerArgs.addAll(
        listOf(
            "-linker-options",
            "-U _FIRCLSExceptionRecordNSException " +
                "-U _OBJC_CLASS_\$_FIRStackFrame " +
                "-U _OBJC_CLASS_\$_FIRExceptionModel " +
                "-U _OBJC_CLASS_\$_FIRCrashlytics",
        ),
    )
}

[LukasHromadnik]

@joharei thanks for the response. But I'm still getting symbol not found in flat namespace: '_OBJ_CLASS_$_FIRCrashlytics'.
Which method (SPM, Cococapods, Carthage, XCFramework directly) do you use to integrate Crashlytics into the app?

[joharei]

@LukasHromadnik right, I got that one too. You need to make sure you're not importing CrashlyticsLogWriter (or probably any other Crashlytics related from this library) anywhere in the code that you're testing. In my case I had to refactor the way I set up the Kermit Logger.

I'm building a dynamic XCFramework published as an SPM package.

[wellingtoncosta]

Hi guys, sorry for a very late response. Is this still an issue or were you guys able to fix this by applying the linker options mentioned above?