I'm getting a crash in my iOS app, but I have no idea what it means. No stack trace. It's coming fro...

# kotlin-native

[Brian Guertin]

I'm getting a crash in my iOS app, but I have no idea what it means. No stack trace. It's coming from Kotlin native. Anyone seen this?

OS Version:         iOS 14.6

(anonymous namespace)::ExceptionObjHolderImpl: 

0 unknown file unknown method

[Nicklas Jensen]

We’re currently seeing the same error and would be very interested in knowing more about it. Our symbolicated crash logs aren’t very helpful as they claim the error occurs within a file that’s actually completely unused in our project, and the Kotlin related threads don’t contain any calls to code we’ve written 🤔

[Nmrsmn]

Hi @Brian Guertin, @Nicklas Jensen; I know it’s a little late, but have you guys found the cause or a solution? I’m experiencing the same crash (only on release scheme) and without any extra information 😞

[Nicklas Jensen]

"A little late" being 2 years 😂... I guess you could say that. I have zero recollection of this at this time, sorry.

[Nmrsmn]

It was the only pointer I could find so I just hoped that you would have some kind of photographic memory haha

[Nicklas Jensen]

Worth a shot 😉. We probably just rewrote whatever part was giving us these issues. That's our usual strategy to using Kotlin/Native (for iOS) whenever we get an inexplicable error from the Kotlin/Native machinery

[Nmrsmn]

Yeah, for me this problem had to do with compose-ios. Crashlytics didn’t gave us any insights but luckily we could get some crash info in xcode from someone that tested our app which had a way better stacktrace and we were finally able to solve it that way. This info might be helpfull if anybody, like me in 2 years, stumbles upon this thread

[Kashismails]

not two years i guess but only a month . So, @Nmrsmn what exactly was causing the issue?

[Nmrsmn]

@Kashismails sorry for the late answers, I was on holidays. I’ll ask my team later today and i’ll post any info (if any) that I can gather

[Kashismails]

thanks @Nmrsmn that will be helpful

[Nmrsmn]

@Kashismails I’m not sure if this will help you, but for us it had something to do with missing resources in compose on iOS. We made use of cocoapods but we ended up removing cocoapods all together and reverting back to the kotlin multiplatform way of framework inclusion setting FRAMEWORK_SEARCH_PATHS = "$(SRCROOT)/../library/build/xcode-frameworks/$(CONFIGURATION)/$(SDK_NAME)";

My colleague made the PR and this is what I found. He told me he used https://github.com/JetBrains/compose-multiplatform/pull/3340 as a reference

[Nmrsmn]

Also; We had the luck some people were testing this feature in testflight and we could use xcode organizer to find the specific crash report which gave us the insights to solve it as the Crashlytics info was rubbish:

Our stacktrace looked like this (I redacted the app and some stuff since my client doesn’t want to get this out in the open):

[Kashismails]

@Nmrsmn thanks this makes sense we do have a problematic resource, i think its finally time to fix it