Fixed
Status Update
Comments
fr...@gmail.com <fr...@gmail.com> #2
Another workaround, getting the ActionBar size at run-time:
TypedValue typed_value = new TypedValue();
getTheme().resolveAttribute(android.support.v7.appcompat.R.attr.actionBarSize, typed_value, true);
swipe_refresh_layout.setProgressViewOffset(false, 0, getResources().getDimensionPixelSize(typed_value.resourceId));
TypedValue typed_value = new TypedValue();
getTheme().resolveAttribute(android.support.v7.appcompat.R.attr.actionBarSize, typed_value, true);
swipe_refresh_layout.setProgressViewOffset(false, 0, getResources().getDimensionPixelSize(typed_value.resourceId));
fr...@gmail.com <fr...@gmail.com> #3
I am experiencing this too...
al...@gmail.com <al...@gmail.com> #4
Another workaround might help
handler.postDelayed(new Runnable() {
@Override
public void run() {
initiateRefresh();
}
}, 1000);
handler.postDelayed(new Runnable() {
@Override
public void run() {
initiateRefresh();
}
}, 1000);
sm...@gmail.com <sm...@gmail.com> #5
same problem here.
am...@google.com <am...@google.com> #6
Same issue here. I am calling an AsyncTask (that calls setRefreshing) from onResume.
fr...@gmail.com <fr...@gmail.com> #7
Same here. android.support.v4 v 21.0.0
fr...@gmail.com <fr...@gmail.com> #8
Problem still exists with android.support.v4:21.0.3.
am...@google.com <am...@google.com> #9
[Comment deleted]
sm...@gmail.com <sm...@gmail.com> #10
[Comment deleted]
il...@google.com <il...@google.com>
al...@gmail.com <al...@gmail.com> #11
FWIW: a workaround that seems to work (even without the delay):
final boolean refreshing = true;
swipeToRefreshLayout.post(new Runnable() {
@Override public void run() {
swipeToRefreshLayout.setRefreshing(refreshing);
}
});
final boolean refreshing = true;
swipeToRefreshLayout.post(new Runnable() {
@Override public void run() {
swipeToRefreshLayout.setRefreshing(refreshing);
}
});
pe...@gmail.com <pe...@gmail.com> #12
[Comment deleted]
Description
Version used: 25.1.0
Devices/Android versions reproduced on:
Nexus 4 Nougat API 25
The issues happens when the MediaControllerCompat is created with the token of the a MediaSessionCompat which has its lifecycle bind to the application.
Here is the LeakCanary log:
In br.com.me.mediacontrollercompatreprocase:1.0:1.
* br.com.me.mediacontrollercompatreprocase.AnotherActivity has leaked:
* GC ROOT android.os.ResultReceiver$MyResultReceiver.this$0
* references android.support.v4.media.session.MediaControllerCompat$MediaControllerImplApi21$1.this$0 (anonymous subclass of android.os.ResultReceiver)
* references android.support.v4.media.session.MediaControllerCompat$MediaControllerImplApi24.mControllerObj
* references android.media.session.MediaController.mContext
* leaks br.com.me.mediacontrollercompatreprocase.AnotherActivity instance
* Retaining: 48 KB.
* Reference Key: c72cb728-7e92-4fce-959a-b2a856ea7af6
* Device: unknown Android Android SDK built for x86_64 sdk_google_phone_x86_64
* Android Version: 7.1 API: 25 LeakCanary: 1.5 00f37f5
* Durations: watch=5013ms, gc=112ms, heap dump=3237ms, analysis=18682ms
For more details, you could use the following sample to reproduce it.