2.0 Evolution

[GLinnik21]

Hello KSCrash Contributors,

As an active contributor to KSCrash, I'd like to propose some significant changes for our upcoming 2.0 release. These changes are designed to improve the modularity, usability, and flexibility of our library. We are currently coordinating these efforts in the release-2.0 branch.

Here are the key tasks I think we should focus on:

• Refactor SPM Modules #462
• Update Podspec to the new project structure #465
• Fix obfuscated pointers #470
• Update deprecated code #466
• Fix unit tests and add CI jobs #467
• Split Privacy Manifest by modules #482
• Discussion on Implementing Opt-Out Mechanism for NSFileSystemSize #491
• Improve Swift generated interface
• Do we really need Android support?
• Configure GitHub Actions for Release Cycle #485

I encourage all contributors to join in this discussion and help us shape the future of KSCrash. Your expertise and feedback are invaluable.

[kstenerud]

Wow I'm VERY impressed! Yes, this sounds very nice!

KSCrash was built when the Apple ecosystem and development environment looked very different to how it looks today, so a facelift is definitely in order.

Android support was only ever in its infancy, and I never got very far on it before I ran out of free time to work on it. The original theory was to have a base "recording" module with sub-modules for the various platforms, and then the "reporting" module would be the same everywhere. But yeah, not much got written for Android so there's not much use in keeping it around (unless someone wants to actually DO that part ;-)

[GLinnik21]

@kstenerud I've seen in your commit messages that you tried to make KSCrash as POSIX-compatible as possible. What was that for, and does it need to be supported now?