diff options
author | Adam Powell <adamp@google.com> | 2014-05-30 12:32:18 -0700 |
---|---|---|
committer | Adam Powell <adamp@google.com> | 2014-05-30 12:32:18 -0700 |
commit | bf06fa047954e85cf9df554d0b3d4eb4b19a950e (patch) | |
tree | 1aa12ef50cae29259af0b5f41626fa51b8695006 /tools | |
parent | eec8f0cbbba8cfe3de29fef4b2362af3817ea575 (diff) | |
download | frameworks_base-bf06fa047954e85cf9df554d0b3d4eb4b19a950e.zip frameworks_base-bf06fa047954e85cf9df554d0b3d4eb4b19a950e.tar.gz frameworks_base-bf06fa047954e85cf9df554d0b3d4eb4b19a950e.tar.bz2 |
Compatibility fix for apps that construct Notification.Builders early
Some apps in the wild are known to construct a Notification.Builder
from within their Activity constructor, passing said Activity instance
as the Context parameter. However at this point in the Activity's
lifecycle the ContextWrapper's base context has not yet been populated
and most calls to Context methods will fail.
Even though this was technically undefined behavior in the past, as
apps have little to no way to guess at these internal implementation
details it's probably best to preserve old expectations. Add a note
in Notification.Builder for future framework developers and remove the
offending call - the associated field was never used anyway.
ಠ_ಠ
Change-Id: I4cf3df10be14739babc8ae9a969d261a7ecf8beb
Diffstat (limited to 'tools')
0 files changed, 0 insertions, 0 deletions