The deadline is today which is 30th June 2020. Check the article here https://developer.apple.com/news/?id=03262020b If you don't go with this, your App Store submissions would get rejected For resolution of images, just go ahead with what resolution your images are based on the desired dimensions. In addition to that have a 2x and 3x scaled images included in your assets. That would work fine.

Is the app clip size restriction on the compressed or the uncompressed version of the IPA? According to my knowledge, as the compressed version of app gets downloaded on the device, so I am thinking that the compressed IPA should be at most 10 MB. Am I correct?

No widget can be added from widget centre / add widgets view. This doesn't work in Xcode 12 beta 1. Even the new applications created on the beta 1 doesn't allow new widget to get added to home screen. Get the Xcode 12 beta 2 for the applications to show up in widget controller centre. It worked for me. I have created new applications with widgets, and they are now showing up in the simulators. Whereas previously in the older beta, they didn't show up.

I think that would violate the HIG's. According to my understand from the designing widgets WWDC video, your widget should show information which is bound to change in your application. Which thereby saves users time to view this glanceable information at a peek on their home screen rather that wasting few minutes to open app and navigate to such view. These widgets would be deep linked directly to your app flow appropriately. I recommend following this video which is very helpful: https://developer.apple.com/videos/play/wwdc2020/10103/

When widget is added to home screen, that is the time when Provider.timeline method gets called. In other cases for display higlight, its just Provider.snapshot method which gets called.

If you don't pass any timeline entries, then widget will be showing redacted view(placeholder view). Snapshot method is solely for the purpose of explaining to user of how the widget will look like? Timeline method is the actual method which will show content on these widgets. You need to pass multiple entries to the callback method, which in-turn renders your views according to the date entries that you have passed. In your case, implement the timeline method and pass some entries, thereby you can see your widget views rendered.

It's hard to know exactly when the system calls the widget timelines request or view rendering. It has happened to me too. The reason is that Either this is due to the beta version of Xcode. In earlier betas like beta 1, the timeline function sometimes did not get called at all for me. But in later betas, the timeline function got called, its an on and off situation. But one thing I have observed in the beta is that the refresh didn't happen at the exact moment of he timeline that I have passed. Or either it could be that way that these widgets work. Sometimes a widget is not deemed to be that important. Maybe the widget was not intensively used/viewed by the user. I have no clue on how apple does it, maybe machine learning, but that thing is that system will call the timelines method based on the apps frequency count or based on widgets usage.

Its the video from WWDC 2020 Video is regarding "Broaden your reach with Siri Event Suggestions" Video Tag : wwdc20-10197 Train Reservation timing in the video - 17:20 Trip Reservation timing in the video - 18:11 Hi Claude. here are your details If you had followed WWDC 2020 videos at all, then you would have understood what placeholder views are. I suggest you check out all SwiftUI videos. SwiftUI views have redacted/placeholder views for all the UIElements. In this video, at the above times, demo applications display certain UI. Just curious on how developers at apple have achieved it?

Deep linking from widget to parent app is very easy. You just have to configure your small widget with widget URL and other widgets with Link view builder. After doing this, when you tap on your widget or specific tap targets of your widget, your App delegate application: openURL method gets called. Be it swift or objective-C, this method will trigger and you have to handle the logic to show a specific application View controller

Embed and sign any external libs/frameworks to the extension target. The widget will then run without any error. It worked for me perfectly.