This weekend happens is that we usually do it twice a year and now (finally) we are considering after many years that it is a false energy saving maneuver, to change the time. In this case, the good thing about changing the time is that at dawn from Saturday to Sunday we will have to set the clock back one hour and therefore at 3 in the morning in our country it will be 2.
This wouldn't be news to Actualidad iPhone if it weren't for the fact that the time change that occurs can fully affect our smart watches. And at the beginning of the month some Apple Watch Series 4 users residing in Australia witnessed a problem of constant reboots on the device after the time change.
For now we can be calm since it was not something generalized and not all Australian users experienced the failure on their watches since it was related to the Activity complication and not all of us have it, but this could be a problem unless Apple remedies with a new version.
The problem is caused by the time change automation itself, something that causes some of the Cupertino clocks to loop and automatically reset themselves constantly. Hopefully this bug doesn't affect our watches this weekend. A few years ago I remember something similar happened with a new version of iOS released for the iPhone, this eliminated the alarms and therefore a good handful of users fell asleep arriving late for their work. In this case things are somewhat different, and hopefully with the current version released by Apple 5.0.1 this is solved, we'll see what happens.
But this was not already fixed with 5.0.1 ??
Just in case, I'll remove that complication.
All the best