Fixed
Status Update
Comments
il...@google.com <il...@google.com>
pe...@gmail.com <pe...@gmail.com> #2
Here is a leak example for a real-life use case. Again, the MediaSession was released, but the leak sticks around:
* GC ROOT android.support.v4.media.session.MediaSessionCompat$MediaSessionImplApi21$ExtraSession.this$0
* references android.support.v4.media.session.MediaSessionCompat$MediaSessionImplApi21.mSessionObj
* references android.media.session.MediaSession.mController
* references android.media.session.MediaController.mContext
* leaks com.bubenheimer.rucksack.d.q instance
* GC ROOT android.support.v4.media.session.MediaSessionCompat$MediaSessionImplApi21$ExtraSession.this$0
* references android.support.v4.media.session.MediaSessionCompat$MediaSessionImplApi21.mSessionObj
* references android.media.session.MediaSession.mController
* references android.media.session.MediaController.mContext
* leaks com.bubenheimer.rucksack.d.q instance
[Deleted User] <[Deleted User]> #3
Thank you for your feedback. We assure you that we are doing our best to address the issue reported, however our product team has shifted work priority that doesn't include this issue. For now, we will be closing the issue as won't fix obsolete. If this issue currently still exists, we request that you log a new issue along with latest bug report here https://goo.gl/TbMiIO .
pe...@gmail.com <pe...@gmail.com> #4
deleted
da...@gmail.com <da...@gmail.com> #5
Can you please confirm whether this is still reproducible on API 33?
And if you happen to have access, also on the Developer Preview of API 34?
il...@google.com <il...@google.com> #6
deleted
il...@google.com <il...@google.com>
il...@google.com <il...@google.com> #7
Final thing, is this a dup of
su...@gmail.com <su...@gmail.com> #8
Thanks, I believe it's a dup at this point.
The other issue was marked as fixed a year ago, but is still as reproducible as ever, I had just tested it on API 33 and UpsideDownCake DP2.
Description
Version used: 1.0.0-alpha01
Devices/Android versions reproduced on: -
Overriding onSupportNavigateUp() helps with the up button behaviour in the navigation architecture components, which is great. However if you have multiple activities the up button does not navigate up to the previous activity. It would be great if it would support that, especially for the migration to the navigation component.