This is also happening to me, no idea why this is happening

@eskimo, is it not a good idea to have concurrent network requests for the widget while the phone is locked? Or in general?

Something I noticed as well is that when the phone screen is locked, populating the data for the widget fails and defaults to the place holder. But whenever the phone is unlocked, it has not problem populating the data.

@eskimo I removed the 3rd party library causing this, and the crashes are still occurring. We're doing no other SQL work either. I can't get the crash reports, because we are testing this via firebase. Is it not recommended to use any 3rd party libraries in widgets at all? The only thing I can think of is that our network requests are potentially causing this crash - but if there are network request failures occurring, the crash reports are not catching them. What else can I do here?

@Eskimo, here it is! crashlog - https://developer.apple.com/forums/content/attachment/976581cb-fc4c-4d6f-b60c-dbbf0290fd22

So the problem was this: https://developer.apple.com/forums/thread/650333 It's why it was working when testing, but not live.

One thing to note about my initial question, we share code between the gallery and the timeline provider delegate functions. So it's the exact same code. So we did the reverse of this problem, and I wonder if this is causing the same issue - https://developer.apple.com/forums/thread/661247

This is still happening - any one got any ideas why?

Figured it out - needed to run the main target scheme, not the widgetextension scheme, oddly enough.

So I think I figured out a potential solution ...originally with beta 1 when my project was created, the scheme included the Intent configuration target in the scheme build step....when I removed this, it seems to have stopped spitting out this error. I'm not sure if the configuration target needs to be included for this to work, but so far it doesn't seem so.

I figured it out. The scheme that I was using was originally intended to handle the WidgetKit Intent configuration. So in the scheme itself, it had a "Siri Intent Query" inside the run step. So all I had to do was create a new scheme that was intended to test the Widget, and the query was no longer there. It then ran without triggering it.

@ricob, thank you for providing that! Extremely helpful. However this would only work with systemMedium/systemLarge Widgets - how would you go about doing this for the small widget? For context, I'm trying to track analytics to determine which Widget size our users get the most benefit from. Any ideas on how this would be possible? Thank you!

This is still happening for me, none of the provided solutions have been able to resolve it either. Simulator iPhone 8 macOS Version 10.15.6 (Build 19G2021) Xcode 12.0 (17210.1)

How were you able to test triggering application(application,didFinishLaunchingWithOptions)? When I run the widget, it's its own target and doesn't seem to trigger any breakpoints in my app delegate.