Post not yet marked as solved
Same here. Tried setting build numbers manually and creating a brand new workflow. Nothing helped.
Post not yet marked as solved
Answering my own question hoping it will help somebody else in the future:
Make sure you specify the bundle argument in NSLocalizedString. Otherwise it will default to Bundle.main. You need to use the bundle of your shared framework for the correct strings to be used.
Post not yet marked as solved
Beta 4 seems to have fixed this issue.
Answering my own question:
Xcode was auto-resolving WidgetKit and implicitly adding it as a required framework. Adding it manually as an optional framework fixed the issue.
Hope this helps somebody.
Post not yet marked as solved
You should look into:
if #available(iOS 14.0, *) {
WidgetCenter.shared.reloadAllTimelines()
}
Post not yet marked as solved
You cannot use UIKit views in WidgetKit. Your widgets need to use pure SwiftUI because the timeline entries get serialized.
Did you try using the normal .blur() view modifier?
Post not yet marked as solved
This seems to be a bug. I created a new Xcode project and added a WidgetKit extension with ConfigurationIntent. Still does not work.
Post marked as Apple Recommended
TimelineProvider now has placeholder(with: Context).
Answering my own question: This works just fine. Here is a great tutorial on how to use URLSessions in widgets. (tl;dr: no special considerations necessary) (This does not allow me to link the URL but search for Oliver Binns WidgetKit)
In my case the problem was because with data from the network, my widget was running against the 30MB memory limit.
Post not yet marked as solved
No. This use does not seem to be possible. You can add a deep-link to your "to battle!" button to open the app to the battle screen but that's just about the limit of interactivity you can achieve with widgets.
We have the same problem. It seems like `supportedFlashModes` is removed from `AVCapturePhotoOutput` documentation as well.I think this is just a bug with the GM and will be fixed in the final release. For the time being the workaround is to use the undocumented `__supportedFlashModes` instead.
