Hello,
I noticed a very interesting behaviour of complications containing strings. When the content of a complication exceeds a number of signs, the device hangs and the only way to make it work again is to hard reboot it. This applies to both templates and current timeline entries. The number of signs depends on the complication family - for modular small it is about 6 signs when the font is set to bold. I didn't check the exact numbers for other families as it takes a lot of time to generate a string, reboot, etc. But it happens in all families.
Has anyone noticed such a behaviour? How did you cope with that?
Is it a bug or feature? I don't think it should be treated as a feature. The strings should get trimmed so that the string is chopped at the end. It should not lead to hanging the entire device...
Interesting, this sounds like a bug with textProviderWithFormat: then, as I have passed longer strings and not seen crashes, but I was not using textProviderWithFormat:.
If you use the NSString creation with format, then pass it to:
[CLKSimpleTextProvider textProviderWithText: (yourstring) ]
Does that work for you? I have passed longer strings on the watch and they are just cut off using this method.