User Profile

Posts

Posts

Post not yet marked as solved
1 Replies
0 Views
Replied In Complication experiencing odd behaviour for only one user
After the user restarted their watch that one seems to be working fine. Now they are having an issue with a different complication that was working before. When WatchOS kills the complication for taking too much CPU time, how long before it is able to "update" again? Not sure that is what is happening since these are very simple complications that share the same data so it's very odd that 4 of them work fine on the same watch face, yet one seems to always have an issue for them. They are the only user with the issue currently.
Post marked as solved
3 Replies
0 Views
Replied In WatchKit Complications not syncing from iOS Watch app
UserInfo in complications only supports Swift Strings for both the key and value. Seems like a bug to me, but this is the only way for them to actually work.
Post marked as solved
3 Replies
0 Views
Replied In WatchKit Complications not syncing from iOS Watch app
Looks like if userInfo is included in the CLKComplicationDescriptor they don't sync between the watch and iOS Watch App, however removing userInfo from my descriptors causes them to work as expected. Is this a bug? What is the point of userInfo if you can't even use it. EDIT: After some further investigation and testing it looks like the only thing that works in the userInfo dictionary is string types. Adding unsupported data types causes an exception stating it needs to be one of the base NS types (NSData, NSString, etc). However even with those types it fails. The only way I can get it to work is by using Swift strings for the key and value.