| commit | 53fafdfbe76d3eeb0fe6782873a03869167a65b0 | [log] [tgz] |
|---|---|---|
| author | Adam Lesinski <adamlesinski@google.com> | Wed Aug 03 13:36:39 2016 -0700 |
| committer | Adam Lesinski <adamlesinski@google.com> | Wed Aug 03 14:44:52 2016 -0700 |
| tree | d51e96ee5b3ba60e047fee259903438d4d81f153 | |
| parent | 76af60554ca5c74a8327774fdc4bf758f7eb518f [diff] |
ResourcesManager: Return null on failure to create Resources A lot of calling framework code expects a null value on failure, and didn't catch the previous exception. There were some strange corner cases where previously a null value was not checked for in framework code, allowing the null Resources object to be returned to the caller. Introducing an exception changed the semantics and can crash certain apps. Bug:30422475 Change-Id: I51d34ae43c9ec605a8790989c56cf85b815ff5b8