Officially Support iOS Widget

[jrosen081]

Problem Statement

We started trying to add Sentry to our iOS Widget, but were unable to based on a series of crashes. It would be awesome if we could get Sentry to officially support the iOS Widget, so that we can safely add it to our widget to get observability.

Solution Brainstorm

No response

Are you willing to submit a PR?

No response

[brustolin]

Thanks @jrosen081 for reaching out. Improving support for Widgets is something we plan to do but I can't give you an ETA.

Can you share some of the crashes you have experienced?

[philipphofmann]

This is slightly related to https://github.com/getsentry/sentry-cocoa/issues/3616, because that issue included adding a sample widget to our sample app.

[ncipollo]

Thanks @jrosen081 for reaching out.

Improving support for Widgets is something we plan to do but I can't give you an ETA.

Can you share some of the crashes you have experienced?

Hi @brustolin - the specific issue we were hitting was https://github.com/getsentry/sentry-cocoa/issues/3513. We had reached out to the support team at sentry to check if crash reporting was supported via sentry currently and they told us it was not (and to file a request here).

We were experiencing a separate issue at the time where our widget would go blank after an App Store update and stay blank, but that has persisted since we've removed sentry from our widget.

You mention that improving support is planned at some point in the future, does that imply there is some baseline support now?

[kahest]

Hey @ncipollo - while we don't officially support widgets as of now, we expect basic functionality like error reporting to work, and we know customers and projects that use it. We fixed https://github.com/getsentry/sentry-cocoa/issues/3513 in release 8.18.0, did you give that a try?

As mentioned above, we will invest some time to establish proper official support, but we don't have an ETA for this atm. However, if you have specific issues/crashes, we're happy to investigate/fix them with higher priority, especially if they impact non-Widget use cases as well.