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, is it not a good idea to have concurrent network requests for the widget while the phone is locked? Or in general?

@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?

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