Hangs and Unresponsive Behavior in App Crashes (Ditto SDK and Rust 1.65+ on Apple arm64 Devices) about plcrashreporter

[AnatolyPristensky]

Hello @konstantinbe,
I was able to reproduce your issue. Investigating, will update this thread once get results.

[MikhailSuendukov]

Hi @konstantinbe and thank you very much for the detailed information. Unfortunately, I was unable to open your project with XCode 14.3.1. It is possible that the file is broken. Could you please fix it or maybe rebuild the project, so I can test it on my side?

[konstantinbe]

@MikhailSuendukov thank you for trying it out. There are two things at play here:

1. After installing git lfs, you have to call git lfs install separately. Here is what brew says:

If I leave this part out, I get exactly the error as you previously posted.

2. Everything in the CrashReporterFreeze is apparently git-lfs-ed. The migration script didn't work as I expected it to. Only the large binary files (DittoObjC) should be lfs-ed.

I've fixed the repo, please try again and make sure to run git lfs install first. Please let me know if you still have problems and I'll be happy to assist further.

[MikhailSuendukov]

It's very strange, but I still get this error. I use these commands to clone your repository:

git lfs install
git clone https://github.com/getditto/CrashReporterFreeze.git

After that I try to open the project file and the same error appears.

[konstantinbe]

Strange, sorry for the trouble. I've uploaded a non-LFS version of the repo to S3:

https://konstantinbe.s3-eu-central-1.amazonaws.com/Shared/CrashReporterFreezeNoLFS.zip

Could you try that?

[okdistribute]

Thank you for taking a look!

[AnatolyPristensky]

@konstantinbe I've spent a lot of time on digging into this issue and it's really hard to identify a root cause. It mainly happens due to integration of DittoObjC library which is built with a particular Rust version. Probably you should ask about your case in the Rust repository as well. For now, this issue has low priority and I'm closing it as won't fix.

Also, we always welcome any contributions.

[konstantinbe]

@AnatolyPristensky thank you for taking the time to dig into this. 💚 We'll try to raise this with the Rust folks and take it from there.