This solved my issue with ClockKit -> WidgetKit migration. Thank you very much! 🙇♂️
Serzhas
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
Post
Replies
Boosts
Views
Activity
Unfortunately, only Apple could answer that question... 🤷♂️
We didn't have any issues in SwiftUI with fonts. What you describe looks like .minimumScaleFactor() modifier in action, rather than issue with fonts. Try adding .fixedSize() modifier to affected view and see if it "fixes" the issue.
Couldn't say better myself! But we have what we have, unfortunately... 🤷♂️
We have many different sizes in our app and many are affected by this issue. Also, I have created a sample project to reproduce the issue, it also has wide range of sizes.
BTW, if you attach a debugger to your Widget Extension process it will update properly. Try it, and you will quickly validate whether stale data is your issue or not. Run your app on simulator, add your widget to Home (or Lock) screen, and then go to Debug -> Attach To Process and select your Widget Extension process (it should be listed on top at the "Likely Targets" section). https://mastodon.social/@brianmueller/111026274124701811
Not sure about your project, but in my case problem wasn't stale data in UserDefaults (App Group), but rather the fact, that widget TimelineProvider is not called to update widget data. I never experienced stale data during development or testing, so I highly double that you have that in your project 🤓