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?
People use bricked incorrectly way too often. Leading to others wondering if they actually mean it is as functional as a brick or that it just crashed and thus can be rebooted or restored. Then again I haven't personally bricked a device in a long time.
Found a nice bug in IOS today, bricks your phone and kills the Simulator
31–35 of 35 posts
Re: Found a nice bug in IOS today, bricks your phone and kills the Simulator
#32Re: Found a nice bug in IOS today, bricks your phone and kills the Simulator
#33Earlier quoted context omitted.
alarm.repeatInterval = NSEraCalendarUnit Triggers the bug, its totally valid as well.
So basically the repeatInterval is expected to have one of the values of an enumeration assigned to it, where the enumerated values are calendar units (representing daily, weekly, monthly, etc.), and it somehow mishandles the value representing "once-per-era"?
Re: Found a nice bug in IOS today, bricks your phone and kills the Simulator
#34Earlier quoted context omitted.
People use bricked incorrectly way too often. Leading to others wondering if they actually mean it is as functional as a brick or that it just crashed and thus can be rebooted or restored. Then again I haven't personally bricked a device in a long time.
> Heretofore, "to brick" can brick anything . http://apple.slashdot.org/comments.pl?sid=423338&cid=221...
Re: Found a nice bug in IOS today, bricks your phone and kills the Simulator
#35Also here is a nicer version that still triggers the bug http://www.pastie.org/private/8a48wgmcuuhjjwbupbk3g