Right now, I am adding the KMM to the library like this: 1. Project file: Add the path the podspec file generated by KMM gradle 2. run pod install 3. It added the KMM module as a cocoapod int he development pod folder 4. Then I referred to that development pod in the podspec file of my ios library (development pod) this way:

s.dependency 'accesstokenmodule'

The logs should show why the crash happens.

This is consistent with any function I tried calling which is in that Kotlin module.

There are no logs at all. thats why its so hard to track down a solution I guess.

My first assumtpion was maybe KMM only supports integration with an ios app and not in the development Pod?

Just an update, We were able to resolve the issue. It looks like the integration with the development pod is possible. The only thing to take care of is that the KMM is available by the time we try to instantiate it. As an example, if my KMM has a

class Foo

with a function

getFooString()

. I need to make sure that by the time I instantiate the Foo class as `private let foo = Foo()`the KMM module should be loaded. More like a race condition. In order to solve it, we added

private lazy var

instead of using

private let

when instantiating the class the very first time. So we wait till we need to use it in the hope that it will be available by then.