@lorihc I'm having problems with WidgetKit migration on WatchOS despite only building that extension for WatchOS 10, can you shed any light on this? Had TSI and Feedback open for many weeks now. Cheers
developer.apple.com/forums/thr

Follow

@HelixApps Howdy! Do you have a FB number I can pass on to the team? (Didn’t see one in the forums thread.)

@lorihc Absolutely, it’s FB12818485. Will get that in the thread too, many thanks 🙏

@HelixApps Hm, that is duped to an issue that was fixed. Will try to figure out what happened.

@lorihc you so much, if there's a work around I need to be doing I'm certainly not aware of it!

@HelixApps Are you seeing this only with TestFlight builds? I examined a 9.6.2 device with both 10.2 and 10.2.1 of your app (from the App Store) and complications installed on multiple faces, and the Widget Extension is properly ignored (it doesn’t run, so it can’t crash).

@lorihc No.. sadly App Store release crashes. Have 100's of 10.2 crash logs. All from app built with Xcode 15.0 RC1. Symptom from users is complications disappearing.
10.2.1 just rolling out so will have those logs soon.

@HelixApps Can you please attach one of those non-TestFlight logs to your Feedback?

@lorihc Just done! Attached to FB12818485.
Any insight on if this is my error/configuration?

@lorihc I've added a WatchOS 9.6.3 crash from the App Store running my app V10.2.1
Still many occurring with WatchOS 9 and not all users are able to upgrade

@lorihc This has been fixed!! or at least a path to a fix is clear 🙏🙏🙏 Thank you....
Now just remains, how to raise awareness on FB10016177, Really important for the future of the WatchOS and WidgetKit platforms with Health access! 🤞

@HelixApps @lorihc We also had done conditional migration for WaterMinder app and lot of tickets for complication disappearance. The crash reports we received from user also similar like this. As report stats "Built for watchOS 10 which is newer than running os", Complication trying to access widgetkit target even for watchos 9 users, causing crash. So last week we migrated watchOS 9 users to WidgetKit, and it seems like no more such crashes.

@HelixApps @lorihc However going through one issue where widgetkit complications not refreshing immediately. Latest beta seems little improved for background transfer, but transferComplicationUserInfo not working for WidgetKit complications like how it works for ClockKit complications, causing delay in showing latest data immediately.

@hiren009 @lorihc Sadly the WatchOS 9 WidgetKit API is missing key features that ClockKit still offers so I really can't migrate OS 9 users, need this bug fixed

@HelixApps @lorihc In our case, handled corner complication differently, Rest of complications achieved.

Sign in to participate in the conversation
CleverLibre Social

CleverLibre Social is an inclusive social instance for open discussion, learning, and community.
All cultures welcome.
Hate speech and harassment strictly forbidden.