alexrparr wrote:
Yes, but what you are saying is a bit ridiculous - of course it’s a bug - not sure why you keep saying that! It would take an apple developer 5 seconds to see that!!!
Because the value 10:09:30 is not a random number, and Apple uses it in its marketing, along with just about every other watch and clock maker.
And, while I never worked for Apple, I’ve bern a paid software developer 50 years, and I’ve seen stranger things intentionally put into software.
For all we know, it is a battery saving issue. Maybe they were expending power updating all the watch faces the user configured, and found they could save power by not doing that, but did not want the time from the last use of that face to be there for the first tick, the chose to store it away with 10:09:30. Or maybe it is a bug from originally eliminating left/right swipe, and the restoration was fast and dirty, with a quick paste of a 10:09:30 image on the display, until the normal watch face code could do the more complex display generation. I do not know, as I do now work on any code that has a GUI interface, but I do know sometimes you find it is easier to let existing code do its thing, that it is to have redundant code initialize the first appearance.
But you have pointed out it has been multiple releases, with an assumed lots of reporting to Apple (not here, as Apple does not look here for bug reports), yet it has not changed. So either the watchOS 10 rewrites made it hard to initially display the current time for 1 second, or it is intentional, or not enough of the over 200 million Apple Watch users have complained to register with an Apple decision maker.