Alarm turned off after daylight savings change?

Daylight savings time WAS NOT LAST NIGHT! It is later in the month!

Sorry you are in Australia. Sorry I thought you were in US. MY BAD.

Everyone with an iPhone in Queensland that I know has been freaking out when they look at the time today.
Apple seems to have stuffed up somehow. Despite the phone time zone being set to Brisbane, not Sydney, the phone is applying daylight saving time.
The fix is to go to Settings>General>Date and Time, and turn off Set Automatically, then turn it back on again.
My Mac has the correct time, so it is an iPhone thing.
I have heard that someone had the same on a Nokia N95, but I don't know if that was a glitch or an incorrect time zone setting.

I would love to see a technical response too.

I live in Queensland, which does not have daylight saving. The time on my iPhone updated yesterday when I switched Set Automatically off then on again. However this morning my weekday alarm set for 5:50 am woke me at 4:50am. The time displayed on the iPhone was 5:50 am. Bizarre. I assume it's a bug, but I can't imagine the problem. Does the iPhone use a different server for repeating alarms?

Same issue on iPhone 4 set to auto update time / date. The alarm was set to 7:00 AM, got triggered at 6:00 AM.
Resetting the phone or deleting and recreating the alarm entry did not help.

Same prob, ip4, os4.1. Recurring alarms not working properly since DST (go off one hr early) . One off alarms working fine. Being reporting at
http://forums.whirlpool.net.au/forum-replies.cfm?t=1546552 as well.

Just mentioned this morning on local Breakfast show too - Sunrise (Ch7). Not looking good Apple.

Hello Apple Technical Support ? Not smart for a smartphone ?

The only fix that AppleCare could tell me was to turn "Set automatically" to OFF in Time & Date settings. I encourage everyone to phone AppleCare and/or send an email via www.apple.com/feedback/iphone.html. What really annoys me is that, judging from these forums, Apple must have known about the problem before daylight savings started in Australia, but chose not to let users know. They would rather wait for bad press to appear in the media.

I live in the US, so I haven't seen this issue yet (our transition from DST is later this month). I am willing to bet that iOS4 has a minor issue in the way it is saving the time for the alarm and the transition to/from DST. People who didn't change their clocks had their alarms go off an hour earlier than expected today. I know that I had experienced a similar problem with the NTFS file system in the past and it was due to an internal API handling of daylight saving time.

My phone did the same thing. I have my alarm set for 6:30am and it's gone off at 5:30am two mornings in a row. I tried resetting the alarm on Tuesday night so that this wouldn't happen this morning, but no cigar. So this morning I connected my phone to iTunes and then once it had finished syncing I turned it off. Fingers crossed this fixes it.

It really just makes me less inclinded to get the iPhone 4 once my contract finishes. There's just way too many problems with it.

Hi Indigored, I'm in Sydney Australia and have the same issue. It appears it hit NZ last week when they switched to Daylight Saving. My repeat alarms all go off an hour earlier than set. Just had a long dull chat with Apple telephone support. The guy I spoke to said I was the sixth Australian he'd spoken to with the same issue today. He advised me that there would be a fix in the next software update via iTunes. He couldn't tell me when this would be. He couldn't put me through to anyone who could tell me when it will be fixed. Best idea he had was to set all my repeat alarms an hour later. Clever!

Brazil - not DST - 1h late

I'm from Brazil, we're not in DST and my wake up alarm now triggers 1 hour LATE. I've been using this alarm for months, I've changed nothing in settings. The bug appeared after upgrading my iPod touch 2nd gen to iOS 4.1. The clock time is correct, the alarm set time is correct, but it triggers 1 hour late.

It seems that because of the structure and communication of Apple corporation, the Apple telephone support staff may not necessarily know any more than a thoughtful user, and almost certainly will know less about this particular alarm issue than a user who peruses these forums. For example, they didn't know that turning off Time Zone Support is another way to temporarily solve the problem (as an alternative to changing Set Automatically to OFF) - something I learnt from an Apple discussion.

This problem was raised in these discussions in June of this year for users in Lithuania and in Sri Lanka. It was New Zealand's turn in late September, and Australia's turn on Sunday. My guess is that Apple will scramble to fix the issue before it hits USA users in November, but why rush until then, when it's only users from other parts of the world (non-Americans) being affected?

There are way too many threads about this.

It looks to be fixed in 4.2 (due in November).
The Early release version has it fixed.

There is not current other fix.
The work around is to set recurring alarms in the calendar and not the clock app.