News for hackers. Stuff that matters.

Fjanth

That would seem to be the case.
Which is why I wrote "OP" in front :)
alarm.repeatInterval = NSEraCalendarUnit

Triggers the bug, its totally valid as well.

Thats not the bug though. Can do it without a loop as well. This was an old version, check the other one I posted here in this thread.
OP:Nope, you didnt read the code. Try reading the other version I posted. Works without a loop as well.
Yeah, I know. Its to bad though because all the discussions are turning into discussions about the proper use of "bricking".
Also here is a nicer version that still triggers the bug http://www.pastie.org/private/8a48wgmcuuhjjwbupbk3g
Im the original poster, that found the bug. Nah it doesnt brick it, it does however require (atleast on 4.1. for me) a factory reset.

The problem seems to be that springboard locks up in an endless loop, restarting the device wont help it because its still loading the offending notification from the cache.