Status Update
Comments
om...@gmail.com <om...@gmail.com> #2
Hi samsadch,
In the AndroidX PDF library, the search view is animated using the
Without this, the callback might be consumed at an upper level, preventing it from being received by the PdfViewerFragment's container.
ra...@google.com <ra...@google.com> #3
Actually the search view is coming but the issue is that it is showing below the Keyboard
om...@gmail.com <om...@gmail.com> #4
Still there
om...@gmail.com <om...@gmail.com> #5
Hey Samsad,
It seems your concern is that the search view remains behind the keyboard when it's open, instead of being positioned below it.
As mentioned in my earlier comment
For reference, you can see the search view translation logic
To resolve this, please ensure that the view hierarchy containing the PdfViewerFragment allows insets to propagate down the view hierarchy.
ra...@google.com <ra...@google.com>
om...@gmail.com <om...@gmail.com> #6
Is there any progress on this memory leak defect?
Description
Hello Team
We found a memory leak in the Android studio profiler heap dump report for the simple case when we finished CarAppActivity every time the memory leak was generated
"carContext.finishCarApp()" after call this it reproduced a memory leak
Is there any why to handle this ?
I am attaching the report and let me know if anything is required from my end