| commit | 68065e0a1980ab6abf8963b48b011efa017fe1c2 | [log] [tgz] |
|---|---|---|
| author | Joe Onorato <joeo@android.com> | Wed Feb 03 20:21:41 2010 -0800 |
| committer | Joe Onorato <joeo@android.com> | Wed Feb 03 20:21:41 2010 -0800 |
| tree | 3d6d4184f359e3bfea6783a97d0de7c2d99d7ab5 | |
| parent | 378a1488bb76d4786025a10e36c2d638cbd2cb6a [diff] |
Fix 1667521 - system process crash after bad notification The steps to reproduce this were kind of interesting. You needed to have a notification with a bogus RemoteViews in the first position in the list, and then have another notification come in with an earlier timestampe. In that case, it would get a bad index for the new (not bogus) view that was being added.