Bug in Clock app: new behavior of alarm in another time zone

[cuttheknot]

Up to yesterday, whenever I set an alarm in the Samsung Clock app, it would always go off in the LOCAL time, even if I created it when I was at home.

Today it had a different behavior and an alarm went off at my home time (I created it at home), although I was abroad, making me miss a bus.

I think this is a new bug, because nowhere I can see the timezone "attached" to an alarm. Moreover, this is really terrible practice of the developer who made this important change without warning users about it. I'm migrating to a new app for alarms: sorry Samsung, but this was enough programming incompetence and unprofessional behavior for me.

[viv_matt]

I'm not sure how you have managed this 🤔, I can only assume you're still set to your home time rather than the local to your current location. Whenever you change time zones, you should be giving the option to keep or change to your current time zone. This is the only way I can see you been affected. Unless as you stated.

[-Robot-]

Not tried on the S25 but my S24 would switch time zone to match where I was and alarm would go off accordingly

Is the time on your phone correct for the location you are at?