|
|
|
|
November 4th, 2010, 16:01 GMT · By Filip Truta
Apple Confirms Plans to Release iOS 4.2 This Week [Updated] |
|
|
|
|
SHARE:
Adjust text size:   |
|
|
Apple has indirectly confirmed plans to roll out the next iOS update for iPhone, iPod touch, and iPad users this week, via a Support document which acknowledges the repeating-alarms bug affecting iPhone owners worldwide.A technical note TS3542 on Apple’s web site entitled “iOS 4.1: Repeating alarms may trigger incorrectly before or after DST change” is, in all senses, Apple’s admission that iOS is suffering from a bug in the alarm clock application. Only those who’ve set their alarms to repeat are affected, and while there is a workaround, the bug will only be resolved by iOS 4.2, the next software update from Apple. Although the Mac maker does not specifically mention the software update itself, nor does it specifically state a release date for a future iOS update, the wording in Apple’s Support document indicates that iOS 4.2 is due out by November 7.
Softpedia has reproduced the contents of tech note TS3542 below, highlighting the indirect confirmation from Apple in red. Symptoms
In some regions, shortly before or after the daylight saving time (DST) change, repeating alarms created in the Clock app may work incorrectly.
Products Affected
iPod touch (4th generation), iPod touch (3rd generation), iPhone 3G, iPhone 4, iPhone 3GS, iPod touch (2nd generation)
Resolution
To resolve this behavior for existing alarms, set the repeat interval to Never. You will need to reset these alarms for each day you need them.
After November 7th, 2010, you can set your alarms to repeat again.What that last line means is that, after November 7th, the bug will be gone. iOS 4.2 being the confirmed November update from Apple, that sentence pretty-much speaks for itself. Softpedia predicted on numerous occasions that iOS 4.2 would be released this week, based on various reports that tracked internal seeding of iOS 4.2 beta builds. Update: Apparently, Apple was only referring to the DST change when the company noted that this timeframe was troublesome, rather than to the actual recurring-alarm bug that should see its fix in iOS 4.2. The update is, nonetheless, on track for a November release. Although this report was appropriately based on more than one factor indicating iOS 4.2 would be publicly released last week, we apologize for any confusion caused.
|
|
|
|
TELL US WHAT YOU THINK:
|
18,157 hits
· 27 comments
· Link to this article
· Print article
· Send to friend
· Subscribe to news
|
MUST-READ RELATED ARTICLES:
READER COMMENTS: |
| Comment #1 by: Chad on 04 Nov 2010, 15:43 UTC |  reply to this comment | interesting....and this has nothing to do with the 7th being daylight savings? |
| Comment #1.1 by: Cam on 04 Nov 2010, 15:56 GMT | This is obviously related to the date that DST ends in the US, not some conspiracy "leak" about when iOS 4.2 will be released. |
| Comment #1.2 by: agathorn on 04 Nov 2010, 16:16 GMT | Yeah I think this "speculation" is off. It wont' affect anyone after Nov 7th because the clocks have changed then. |
| Comment #1.3 by: GAS on 07 Nov 2010, 02:27 GMT | How parochial! What about southern hemisphere folk who have just recently moved into DST? Just because DST ends in the US, doesn't mean the problem goes away!!!!
Here in Australia it will remain a problem until the fix is released. I hope it is next week!! |
| Comment #1.4 by: Khalid on 15 Nov 2010, 23:49 GMT | check appl.com
it seems iOS 4.2 coming 16 november 2010 |
| Comment #1.5 by: mot on 19 Nov 2010, 01:40 GMT | how australian! (in response to your "how parochial!")
the problem isn't daylight savings time (or standard time), but the time shift going from dst to standard time. (a recurring alarm that goes across the change is a programming problem.) and that's no different in australia or anywhere else that has dst - the clocks change twice a year.
now back on yer heads, mate! |
| Comment #2 by: cw on 04 Nov 2010, 16:00 UTC | reply to this comment | November 7 is the end of DST in the United States, which is why the bug will not be an issue after that day . |
| Comment #3 by: JCS on 04 Nov 2010, 16:02 UTC | reply to this comment | You assume this means the update will be available by November 7th. I doubt this is what it means. It is more likely that the bug only happens before November 7th. After the 7th the non-patched buggy code will start working again because the bug is dependent on the US DST changeover date which is Novemebr 7th |
| Comment #4 by: russ on 04 Nov 2010, 16:10 UTC | reply to this comment | November 7th is the day that the US daylight saving time changes. |
| Comment #5 by: anonymous on 04 Nov 2010, 16:17 UTC | reply to this comment | This does not confirm the release of iOS 4.2. It's simply the date when DST will be in effect for all regions, thereby removing the condition in which the bug exists. |
| Comment #6 by: Lumo on 04 Nov 2010, 16:42 UTC | reply to this comment | Sorry, won't the bug be gone since Nov 7th simply because it is related to the daylight savings time, and on Nov 7th, America will join Europe and return to the winter time?
I don't think that the text implies the iOS 4.2 release. |
| Comment #7 by: chris on 04 Nov 2010, 17:21 UTC | reply to this comment | my thoughts exactly...the 7th is when DST ends in the US. |
| Comment #8 by: Nic on 04 Nov 2010, 17:22 UTC | reply to this comment | Not necessarily. The bug may only exist for non US locations whilst in US aligned DST. After the 7th the bug may just disappear with a long term fix applied to 4.2 |
| Comment #9 by: JSP on 04 Nov 2010, 20:56 UTC | reply to this comment | "After November 7th, 2010, you can set your alarms to repeat again" doesn't confirm anything as the daylight saving time in US is on Nov 7th. Post DST the alarm will work as usual till next DST change. |
| Comment #10 by: Bubba on 04 Nov 2010, 23:42 UTC | reply to this comment | No.. It has nothing to do with ios 4.2… The US moves off of DST on the 7th.. The bug is a result of Apple not handling correctly the change. US Law made changes to the dates in which the time is rolled forward or back.. Not everyone has made the proper adjustments.. Apparently Apple is one of them.. Nothing more to see here.. Moving on.. |
| Comment #11 by: SerenityLodge on 05 Nov 2010, 00:27 UTC | reply to this comment | or does it simply mean that after the change in Daylight Savings, the bug will not be in play? I don't see anything in the technical note so support your speculation. But, one can only hope! |
| Comment #11.1 by: Steph on 07 Nov 2010, 05:47 GMT | Sorry but i'm in Europe and I've tested the alarm after our DST change... and the bug persist. Try to set an alarm with recurrence and you will see the bug still here after DST change. Set an alarm without reccurence and the bug not affect this kind of alarm. So the bug is not for THE day of DST change in my mind... |
| Comment #12 by: onegoodcop661 on 05 Nov 2010, 15:13 UTC | reply to this comment | Bad assumption. A much more likely interpretation is that November 7th is when DST ends, and the bug will no longer be an issue. It will be fixed by the time DST rolls around again in Spring. That's what the November 7th date means. |
| Comment #12.1 by: mot on 19 Nov 2010, 02:05 GMT | "Bad assumption. ... It will be fixed by the time DST rolls around again in Spring."
worse assumption. wang labs missed fixing a leap year date bug in their operating system THREE leap years in a row! (yes, they were in business for more than 12 years...)
the way software development goes, references to bugs in the future tense are meaningless. |
| Comment #13 by: Tyler on 06 Nov 2010, 03:42 UTC | reply to this comment | Well wouldn't it be logically to release it on this day or before to avoid the problem entirely? Also target is planned to carry iPhone and best buy mobile the iPad on which day? November 7th. In theory those stores could already have iPhones and ipads with 4.2 sitting in their store rooms waiting for November 7th! |
| Comment #14 by: noshitsherlock on 06 Nov 2010, 04:07 UTC | reply to this comment | the 4.2 GM is already out. it was released for developers a couple of days back. so it means itll definitely be out by the end of the week. |
| Comment #15 by: Jim on 07 Nov 2010, 03:29 UTC | reply to this comment | "after November 7" means after the flip away from daylight savings time. |
| Comment #16 by: Rik on 07 Nov 2010, 15:05 UTC | reply to this comment | today is november 7th and still no 4.2 update here greets from Belgium |
| Comment #17 by: Idk on 08 Nov 2010, 14:19 UTC | reply to this comment | Ok well now US users have the alarm bug. Both my girlfriend and her roommate's iPhones went off an hour late. (iPhone 4 and 3GS, both on 4.1) It started on Sunday and it happened today too apparently. So it would make sense for them to release it pretty soon. Unless they want to make more people in the US upset. |
| Comment #17.1 by: dos0711 on 09 Nov 2010, 20:37 GMT | I wouldn't rely on a cellphone as an alarm clock anyways. |
| Comment #18 by: Khalid on 15 Nov 2010, 23:50 UTC | reply to this comment | check apple.com
it seems iOS 4.2 coming tuesday 16 november 2010 |
| Comment #18.1 by: mot on 19 Nov 2010, 02:06 GMT | checking my system's clock, i would say "probably not". |
|
Copyright © 2001-2012 Softpedia. Contact/Tip us at  |
|
Find us on Google+
