Fixed
Status Update
Comments
jb...@google.com <jb...@google.com>
cl...@google.com <cl...@google.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
cl...@google.com <cl...@google.com> #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 .
ap...@google.com <ap...@google.com> #4
deleted
jb...@google.com <jb...@google.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?
jb...@google.com <jb...@google.com>
na...@google.com <na...@google.com> #6
deleted
jb...@gmail.com <jb...@gmail.com> #7
Final thing, is this a dup of
cl...@google.com <cl...@google.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: 2.8.8
Devices/Android versions reproduced on:
Pixel 8 Pro
Issue description:
I have an app with Compose and 2 simple destinations: start destination "home" and deeplink destination "url"
I was able to access the "url" screen by launching:
adb shell am start -W -a android.intent.action.VIEW -d "xiver://
Last 2 fields: "dsfds" and "32" are parameters.
After library update from 2.7.7 to 2.8.8 it stopped working and now only "home" destination is opened.
If this is a bug in the library, we would appreciate if you could attach:
- Sample project to trigger the issue. [ATTACHED]