-
Notifications
You must be signed in to change notification settings - Fork 130
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
Use KSCrash dependency in CocoaPods instead of self-hosting #41
Comments
Hi @orta, For now we have a few unmerged changes to KSCrash. We'll kick off a project to get them merged upstream (it requires a bit of cleanup), so this should be fixed eventually. (That said, Bugsnag will work without those changes, it will just block the UI thread more than we'd like). Conrad |
👍 good luck :) |
We are getting class collision with https://appmetrika.yandex.ru/ , which is quite popular in Russia. Could you please estimate when would you be able to ship fix for that dependency? That is important for us as we will consider forking your library in case it will take another few months for you to fix. |
@gsamat Unfortunately we are still a bit away before we can start this project. I'd recommend forking the notifier for now. |
The following build commands failed: KSCrash compile failed, use command compile |
I agree with @orta on this 👍 Are we any closer to getting that added in? |
KSCrash is it's own independent CocoaPod, people are less likely to get class collisions in their apps. If they are including both ( I am in the tests for ARAnalytics )
The text was updated successfully, but these errors were encountered: