From f37dfff473718491b763d3ffa95db92a3240ce89 Mon Sep 17 00:00:00 2001 From: Eric Castelo Branco Mesquita Date: Thu, 28 Nov 2024 18:10:18 +0000 Subject: [PATCH] Update CrashlyticsTutorial.md fix typo --- website/docs/CrashlyticsTutorial.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/docs/CrashlyticsTutorial.md b/website/docs/CrashlyticsTutorial.md index 60023c6..972e089 100644 --- a/website/docs/CrashlyticsTutorial.md +++ b/website/docs/CrashlyticsTutorial.md @@ -76,7 +76,7 @@ Undefined symbols for architecture x86_64: _co_touchlab_crashkios_crashlytics_FIRCLSExceptionRecordNSException_wrapper0 in result.o ld: symbol(s) not found for architecture x86_64 ``` -This is because on iOS only the definitions for Crashlytics are added when comiling the Kotlin code and building the framework. The binary (the actual Crashlytics library) isn't added until later when you build the iOS app. When building a dynamic framework, the Kotlin compile expects to be able to resolve everything, so you'll see the above error because Crashlytics isn't there yet. +This is because on iOS only the definitions for Crashlytics are added when compiling the Kotlin code and building the framework. The binary (the actual Crashlytics library) isn't added until later when you build the iOS app. When building a dynamic framework, the Kotlin compile expects to be able to resolve everything, so you'll see the above error because Crashlytics isn't there yet. To workaround this, we need to tell the compiler that these symbols are find and will be there later. Doing it manually is a bit messy so you can just add our gradle plugin to handle it ```kotlin @@ -108,4 +108,4 @@ CrashKiOS-crashlytics also provides shared code wrappers for sending logs and c ```kotlin CrashlyticsKotlin.logMessage("Some message") CrashlyticsKotlin.setCustomValue("someKey", "someValue") -``` \ No newline at end of file +```