Fixed
Status Update
Comments
yb...@google.com <yb...@google.com> #2
In activity Log, you have the ability to filter events like this issue [1]. Would that be an alternative to deleting events that may be valuable for debugging ? If not, please explain the use-case.
[1]https://issuetracker.google.com/issues/72574664#comment3
[1]
ad...@google.com <ad...@google.com>
yb...@google.com <yb...@google.com> #3
Thank you for helping us improve the functionality of our products. Your feature request has been forwarded to the product team. You can track this thread for any updates, or post additional comments about the request. However, we cannot provide an ETA or guarantee its implementation at this point in time.
Note: I edited the request to reflect upon [1]. Furthermore, you have the ability to filter such events as suggested above and may help.
[1]https://serverfault.com/questions/915523/how-to-clear-notifications-in-the-google-cloud-platform-
Note: I edited the request to reflect upon [1]. Furthermore, you have the ability to filter such events as suggested above and may help.
[1]
yb...@google.com <yb...@google.com>
ma...@gmail.com <ma...@gmail.com> #4
I am having this issue too. I think the #3 comment is missing the point.
The issue is that as errors or issues occur, the number on the notification badge is incremented. With no way to clear these notifications, the count in the eye-catching red badge just keeps going up and up, making this all but useless as a UI element.
The comment addresses the issue of clearing the event from the activity logs but doesn't address the simpler request to just clear the notification.
The issue is that as errors or issues occur, the number on the notification badge is incremented. With no way to clear these notifications, the count in the eye-catching red badge just keeps going up and up, making this all but useless as a UI element.
The comment addresses the issue of clearing the event from the activity logs but doesn't address the simpler request to just clear the notification.
yb...@google.com <yb...@google.com> #5
ugh looks like it missed 3.4 and only went into 3.5 :/.
i'll try to cherry-pick it into 3.4 but probably too late to catch 3.4 release.
i'll try to cherry-pick it into 3.4 but probably too late to catch 3.4 release.
yb...@google.com <yb...@google.com> #6
i cherry picked it but it missed 3.4 :/. it will be in 3.4.1 (if happens). otherwise, it is already in 3.5
26...@gmail.com <26...@gmail.com> #7
Hi
sa...@gmail.com <sa...@gmail.com> #8
ดี
an...@gmail.com <an...@gmail.com> #10
akses kartu SD
Description
Version used: 3.4.0-alpha09
Devices/Android versions reproduced on:
Pixel 2 XL/Android 9
android.databinding.ViewDataBinding$LiveDataListener.onChanged cause NullpointerException
@Override
public void onChanged(@Nullable Object o) {
ViewDataBinding binder = mListener.getBinder();
binder.handleFieldChange(mListener.mLocalFieldId, mListener.getTarget(), 0);
}
Above code doesn't check nullity of binder which may be null. mListener is a ViewDataBinding.WeakListener, It's getBinder method goes like this:
protected ViewDataBinding getBinder() {
ViewDataBinding binder = get();
if (binder == null) {
unregister(); // The binder is dead
}
return binder;
}
When binder is GCed, null is returned and hence LiveDataListener.onChanged will fail with a NullpointerException.