Ivan Matkov

I've noticed that there is a branch introduces custom section which is very similar with it - `feature/PLCR-527-support-plcrash_info`. It's definitely another feature, but we need to check it out before...

Hi @sevaa, Thanks for getting in touch! Could you please clarify a few things to help understand the case better: 1. How do you get that crash report? What flags...

`PLCrashReporterSymbolicationStrategyAll` means that the library will try to perform local symbolication via all available strategies. 1.4 fixes some bugs in run-time symbolication, so I guess that's why it can find...

@sevaa 1.3 was never properly released Also, see #23 for more information on the current state of the repo

Hi @jindalpatel, I cannot reproduce this issue, could you please share sample application or that corrupted file with crash report? PS I'm going to update protobuf-c dependency where the crash...

Closing it for now since I've already updated the dependency where the crash happens. Feel free to reopen this issue if you have more questions or some additional info that...

Hi there, @Piyush23786 thanks for reproduction sample and for confirmation that it's SwiftPM distribution issue. But we didn't find root cause yet though. We'll let you know when it will...

@Piyush23786 No, we didn't found the root cause yet. Please use CocoaPods instead of SwiftPM for now

@jindalpatel are you using Unity in your project too? It might be a problem with conflict of multiple PLCR versions in the same project. Unity includes PLCR copy with `Unity`...

@tipa it's in our queue after proper .NET 6 support. No exact ETA yet. Of course contributions are welcome here