Those notifications could get into a group with higher priority
because they were autobundled or if the app said so.
This could lead to invisible views on the lockscreen and a crash
when this happened in an animated fashion.
The bug was triggering old code that wasn't needed anymore that
removed the viewstate.
Change-Id: Ic86c2f03d55f2e98e352cdbfbb3ca80d8e676765
Fixes: 28611831
- Previously, the call was made to showRecents() which took a single
boolean to determine alt-tab state, and after the refactoring, it
no longer made the same call.
Bug: 28663474
Change-Id: I75fb793e56c9a094a4372d7157dbd0dd7ecdbda7
ListView was leaving header and footer views
in the detached state, which is a problem because
no view should be left in that state after a layout
calculation. This was also causing the view to never
received detached-from-window callback if
the ListView is detached while the header is not
visible.
This CL fixes an issue by traversing fixed views
and removing the ones that match the criteria.
To keep the behavior as similar as possible,
we still do not call startTmpDispatch on
fixed views unless we'll remove them.
Bug: 24490656
Change-Id: I8acfbd1a9d9b8b24c1c4b7692ef82cfe0f4d43a8
As of Android N, passing file:// URIs across package boundaries
throws a FileUriExposedException. This has caused frustration among
app developers trying to use our example as boilerplate code. This
patch replaces the "take picture" example with one that uses
content:// URIs and FileProvider instead.
Bug: 27636012
Change-Id: I9f0b4d9bbcd6b4bfa770dd1e4ad37f321e22195f
If the app is waiting for an opening animation with a dummy placeholder,
we need to skip the surface placement (in addition to the animateLocked).
Also, when animating is changing from exiting to entering, the mAnimating
flag needs to be cleared until the new animation starts. This prevents the
surface placement to place it wrong before the new animaition starts.
bug: 28599295
bug: 27742244
Change-Id: I26f0ead80ee9993a6c766ae8686ab11d1729519c
We were leaking references in each call to onMessageReceipt(),
leading us to eventually run out of references and crash. We
now delete our local references prior to leaving the function.
Also, since especially our message size can be quite large,
we put in logic to gracefully fail if the system is out of
memory.
In addition, we fix up reference leaks within
constructJContextHubInfo(). These were one-time leaks at
initialization, so not the root cause of our crash, but still
unnecessary leaks which are easily fixed.
Bug: 28655628
Change-Id: I3a3dc8e069c6c1810f3152872d8d8410e8ad0683
Allow removal of replaced window if it isn't running an exit animation
and wasn't set to run an exit animation.
Bug: 28411852
Change-Id: I916d7c9461691bc58367d012113fefe9c6485127
Because notifications could become isolated when
the group is suppressed it could lead to concurrent
modifications while looping.
Change-Id: Ifd4fe0cc24110455de0d3edf2da0be0773eb8c67
Fixes: 28652038
When a child got set not be a heads up after it was already
removed (When for example it was clicked on shortly after
it got posted) then it got orphaned leading to bad bugs
like the next notification not being visible. This
could happen often with WhatsApp who set the head up flags
on the summary instead of the children.
Change-Id: I52c8f5d9bc50080e4ece530255236d36f998372e
Fixes: 28565942
am: 5e42875297
* commit '5e428752971f2e3dfc3fda73633fc346f50f2763':
update redirects for /studio files for the restructure from this CL: https://critique.corp.google.com/#review/121726749
Change-Id: I76513a274909a296589c1354dfc0551764390e72
am: 1a8f9e3ca0
* commit '1a8f9e3ca00fb4436710e34b1f7fb2259adc066f':
update redirects for /studio files for the restructure from this CL: https://critique.corp.google.com/#review/121726749
Change-Id: Id0d7cf68025c8f6b082ebfdec6c9727e963d6b9a
am: ab5bf95626
* commit 'ab5bf95626850e97124b912ca2699fb164574186':
update redirects for /studio files for the restructure from this CL: https://critique.corp.google.com/#review/121726749
Change-Id: I7524aa066efa4241c6a14d881b23dee0da8e2632
- TrustedCredential is responsible to show ConfirmCredential
- Show the MonitoringCerInfoActivity in personal side instead to avoid showing work challenge
- put user id into extra
Bug: 28619980
Change-Id: Iedbc0b721ef56675f3c9eb6f1d12daf1222ad080
We need the attributes to remain public because people might still be
linking against them, but we don't want them showing up in the
documentation any more. Them showing up in the documentation also had
the side effect that it would accidentally mark the parent class of
attributes as @removed, which was not intended.
Bug: 28663748
Change-Id: I2f6eb09455fddf1086e6b24bc3bea5292e8e32b7
At least on android TV emulator system image, the Netd
service could be null when the setDnsConfigurationForNetwork
is invoked.
bug: 28553503
Change-Id: If059495c8573ede287c4e9d8f343318d519fca7f
