Philipp Hofmann
Philipp Hofmann
Hey, @naftaly. We decided on a call that we want to implement the proposals of this PR in increments. We definitely would like to use the memory pressure logic for...
Thanks for the detailed update and all the input @naftaly 🥇.
We are going to pull code from this proposal once we tackle https://github.com/getsentry/sentry-cocoa/issues/3890, but I'm going to close this for now, as we aren't actively working on this right now.
Do you want to be able to use a custom transport to send events to the sentry only via WIFI, @bfpepper87sentry? If yes, please explain your reasons. Maybe we can...
Let's use caching to speed up these GH action workflows. If they are speedy, we can run them for every PR, especially considering the recent interoperability with ObjC to Swift...
P1 is for iOS only. We can delay CI for the other platforms.
Another proposal is to change the exception value to something like: `reason: "it crashed"` and `reason: nil`. So when there is no reason, this clearly communicates this.
We have a proper solution for this with https://github.com/getsentry/sentry-cocoa/pull/4011, but it requires https://github.com/getsentry/sentry-cocoa/issues/4012 which is a breaking change. As 9.0.0 will soon happen, we aren't going with a temporary solution...
> This is still a problem, no? Yes, we didn't merge the PR https://github.com/getsentry/sentry-cocoa/pull/2691 yet.
@brianmichel, I guess it makes sense to start the SDK again for the subprocess, or we add an option to make it configurable wether you would like to get crashes...