Thanks I read that and a watched a few wwdc videos. It just seems that if you're going to use BGBackgroundTask then you're not guaranteed to have a 'live-like' experience. Because the update for a 'live' experience is something that should happen within 2s - 20mins. But with BGProcessingTask it could turn out to be 2hrs when device is idle our end of night when device is charged. Or is it that an app that has a Live Activity gets promoted to have sooner and longer background time?

For a framework, once you strip debug symbols, then what else is there left for you to strip? Why is there another flag for STRIP_SWIFT_SYMBOLS? Does STRIP_SWIFT_SYMBOLS only strip non-external symbols? Like if a framework has non-external, then they're not needed for the main app binary. So you can strip them. Does STRIP_SWIFT_SYMBOLS affect the stripping of such non-debug non-external symbols? Like it will strip anything that's marked with internal, private in your Swift module?

For a framework, once you strip debug symbols, then what else is there left for you to strip? Why is there another flag for STRIP_SWIFT_SYMBOLS? Does STRIP_SWIFT_SYMBOLS only strip non-external symbols? Like if a framework has non-external, then they're not needed for the main app binary. So you can strip them. Does STRIP_SWIFT_SYMBOLS affect the stripping of such non-debug non-external symbols? Like it will strip anything that's marked with internal, private in your Swift module?

I was using a List and I got this error. It seems that anything interactive will cause this bug. References: https://stackoverflow.com/questions/63135404/why-do-some-views-appear-as-a-red-no-entry-sign-in-widgets https://developer.apple.com/videos/play/wwdc2020/10028/?time=707