Found a nice bug in IOS today, bricks your phone and kills the Simulator

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.<p>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.

Does it really "brick" your phone, as in "makes it crash in a way that is completely irrecoverable and that can never ever be repaired, therefore turning your phone forever into a piece of hardware comparable in functionality to a brick" or does it just make the phone crash?

Also here is a nicer version that still triggers the bug <a href="http://www.pastie.org/private/8a48wgmcuuhjjwbupbk3g" rel="nofollow">http://www.pastie.org/private/8a48wgmcuuhjjwbupbk3g</a>

I am not an iPhone developer, but the code doesn't seem unreasonable to me.<p>Can anybody explain what is special about this code?

For people lost in the thread, I've read the whole thing. The actual problem here as posted by the guy who found it (Fjanth in this thread) is that setting a local notification with a repeat value of era breaks iOS and requires a factory reset in order to recover.