-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash on production app #69
Comments
Are you using CrashKiOS with crashlytics or bugsnag? We aren't initially sure what the issue is. Can you share any more context or a small reproducing project? |
Did you solve the problem? |
Thanks for your interest. We're using Crashlytics. Currently, we have decided to leave CrashkiOS since we are not able to solve it fast. I will provide a small project once I have more time. It's not trivial. @dmikots not yet, sadly :( |
We have the same issue as well. Everything works until we upload app to TestFlight or App Store then it just crashes on start without any stacktrace to help us track it down. |
And we are experiencing the same problem as described above. |
Hey everyone, could you try running the app on your device/simulator in Release configuration? It should also crash and should give you a stack trace in Xcode. If you could share that, it'd help us finding a reproducer and a fix. Thank you! |
@TadeasKriz the funny thing is that it does not crash in any configuration or on any device until app is uploaded to TestFlight or App Store. |
Just to doublecheck, following the steps below don't lead to a crash?
|
Does not crash. |
Can you check your "Run Phases" to see if any of them have "For install builds only" enabled? |
None of them have "For install builds only" enabled. |
Thanks, that's good to know. Would you be able to tell us more about your specific project? What libraries do you use and how you have everything configured? |
Its a simple KMM project. We are consuming shared KMM module on iOS through Cocoapods. We do not have any custom configuration. SPM packages used:
|
And on the Kotlin side, what dependencies do you use and how do you have CrashKiOS configured? |
Project is multi-modular. About 100 Kotlin modules and 1 main module (Composition) that combines all of them. This library is integrated according to documentation in that main module. Libraries used on KMM side extracted from libs.versions.toml (not all of these are used, but most are):
|
P.S.: project is using Dynamic linking, so we have integrated co.touchlab.crashkios.crashlyticslink plugin as well. |
Thanks, that's good info. Last thing to try that comes to mind, could you try and compare the I'm basically trying to find whether this happens before it's uploaded to AppStore Connect, or if AppStore Connect somehow breaks it (which shouldn't happen). Oh, and if you could download |
@tomasjablonskis @shatodj @DmitriiVM Do you have more information on this? Possibly a stack trace for the crash, or dyld logs perhaps? |
Hi @TadeasKriz I've got you the crash report (obfuscated a bit) when running iOS app on the Mac OS using the CrashKiOS. The app is working good without the CrashKiOS.
|
This seems to be caused by App Thinning removing the Crashlytics dependency. I think it’s because we’re using We already plan to implement a different workaround by compiling a stub framework and linking against it instead. That way AppThinning will see the dependency and wont remove the symbols. For now you should be able to workaround this by explicitly importing and using Crashlytics in your Swift code. |
@TadeasKriz So I have import FirebaseCore
import FirebaseCrashlytics
// ...
func application(
_ application: UIApplication,
didFinishLaunchingWithOptions _: [UIApplication.LaunchOptionsKey: Any]?
) -> Bool {
configureCrashKiOS()
}
private func configureCrashKiOS() {
// test crashlytics fix
_ = Crashlytics.crashlytics().isCrashlyticsCollectionEnabled()
// configure CrashKiOS in common
IOSDIKt.startCrashKiOS()
} Maybe is good to mention that we are using Firebase SPM package. |
Are there plans to fix this issue? It's the only thing blocking my team from updating our apps to Kotlin 2.0 Thanks :) |
The same thing 😅 |
I was able to reproduce this, it's not app thinning but deployment processing. More specifically the Since this is a larger change, we want to do some more internal testing before releasing it. I'll keep you posted. In the meantime, making your KMP framework static will work around the issue. |
Should be resolved on |
Hi there. Thank you for fixing the crash. There has been some good progress. However, I have another crash in production only with a different trace log. But maybe I'm still missing something.
|
I had the same problem with unresolved symbol, updating the plugin version from 0.8.6 to 0.9.0 seems to have solved the issue. But as OP, I have now stumbled upon a new issue. We are exposing a dynamic framework to iOS, everything is working fine until we archive it and release it on test flight. As soon as we open the app, it crashes. This is the error log from iOS:
|
Hi Touchlab,
I tried to implement CrashKiOS for our project and was successful when the app was built for development on iOS. In the production environment, there was a crash immediately after the app started.
Here is the error I picked up from the Console.
Here is my gradle.build.kts for xcode:
I just have no clue where to look to solve the issue. Maybe you will be able to see the problem here. Thank you for the feedback.
The text was updated successfully, but these errors were encountered: