Fixed
Status Update
Comments
fe...@gtempaccount.com <fe...@gtempaccount.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]
vi...@google.com <vi...@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]
bo...@gmail.com <bo...@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
Looks like this is happening because of b/116541301 .
I'm not sure why changing super class from DataBindingComponent to Object breaks compatiblity though :/.
This was an intentional change to get rid of the million errors problem (details in b/116541301 )
recompiling that library should fix the error.
I'm not sure why changing super class from DataBindingComponent to Object breaks compatiblity though :/.
This was an intentional change to get rid of the million errors problem (details in
recompiling that library should fix the error.
bo...@gmail.com <bo...@gmail.com> #6
To be clear, you mean I should recompile the library with the AGP 3.5.0-alpha03?
yb...@google.com <yb...@google.com> #7
yes. though actually we can just add this support back by adding back that constructor. i'll take a look at it.
id...@gmail.com <id...@gmail.com> #8
> I'm not sure why changing super class from DataBindingComponent to Object breaks compatiblity though :/.
Yigit, it breaks binary compatibility while preserving source compatibility
The corresponding SO issue:https://stackoverflow.com/a/55263109/648313
Yigit, it breaks binary compatibility while preserving source compatibility
The corresponding SO issue:
[Deleted User] <[Deleted User]> #9
We also had the same problem. This happened when we are using a library using databinding and compiled with tools 3.3.
Fortunately the library is owned by us and we just upgraded it to use 3.4 too.
Would be good if this is fixed before 3.4 release actually so that it is backward compatible.
Fortunately the library is owned by us and we just upgraded it to use 3.4 too.
Would be good if this is fixed before 3.4 release actually so that it is backward compatible.
di...@mercedes-benz.io <di...@mercedes-benz.io> #10
3.4 was released today, but the issue was not fixed :(
yb...@google.com <yb...@google.com> #11
ok this is my mistake, didn't re-set the priority so missed it. moving to p0, will see if i can get into 3.4.1.
I'm sorry about it.
I'm sorry about it.
[Deleted User] <[Deleted User]> #13
When is the 3.4.1 release scheduled?
da...@google.com <da...@google.com> #14
Unfortunately, I can't speak to a release date, sorry about that. Releasing 3.4.1 is something that's actively being worked on.
Usually what I recommend in general is looking at our historical release schedule and estimate from there:https://en.wikipedia.org/wiki/Android_Studio#Version_history
Usually what I recommend in general is looking at our historical release schedule and estimate from there:
id...@gmail.com <id...@gmail.com> #15
Is this fix also included in 3.5 Beta 1? If no, is it planned to be included in 3.5 Beta 2?
yb...@google.com <yb...@google.com> #16
it should be in beta1
Description
com.android.tools.build:gradle:3.2.1
works as expected. Using:
com.android.tools.build:gradle:3.4.0-beta01
results in an runtime error when the data binded activity is loaded:
java.lang.NoSuchMethodError: No direct method <init>(Landroidx/databinding/DataBindingComponent;Landroid/view/View;I)V in class Landroidx/databinding/ViewDataBinding; or its super classes (declaration of 'androidx.databinding.ViewDataBinding' appears in /data/app/com.heb.hebpaytestapp-Hn4yutXMac9p1ltUJnjzoQ==/split_lib_dependencies_apk.apk)
at com.heb.paysdk.databinding.HebPayActivityAddCardBinding.<init>(HebPayActivityAddCardBinding.java:107)
at com.heb.paysdk.databinding.HebPayActivityAddCardBindingSw400dpImpl.<init>(HebPayActivityAddCardBindingSw400dpImpl.java:258)
at com.heb.paysdk.databinding.HebPayActivityAddCardBindingSw400dpImpl.<init>(HebPayActivityAddCardBindingSw400dpImpl.java:255)
at com.heb.paysdk.DataBinderMapperImpl.getDataBinder(DataBinderMapperImpl.java:77)
at androidx.databinding.MergedDataBinderMapper.getDataBinder(MergedDataBinderMapper.java:74)
at androidx.databinding.DataBindingUtil.bind(DataBindingUtil.java:199)
at androidx.databinding.DataBindingUtil.bindToAddedViews(DataBindingUtil.java:327)
at androidx.databinding.DataBindingUtil.setContentView(DataBindingUtil.java:306)
at androidx.databinding.DataBindingUtil.setContentView(DataBindingUtil.java:284)
at com.heb.paysdk.addcard.AddCardActivity.onCreate(AddCardActivity.java:53)
at android.app.Activity.performCreate(Activity.java:7136)
at android.app.Activity.performCreate(Activity.java:7127)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1271)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2893)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:3048)
at android.app.servertransaction.LaunchActivityItem.execute(LaunchActivityItem.java:78)
at android.app.servertransaction.TransactionExecutor.executeCallbacks(TransactionExecutor.java:108)
at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:68)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1808)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:193)
at android.app.ActivityThread.main(ActivityThread.java:6669)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)
Build: 3.4 canary 10, AI-183.4588.61.34.5202479, 201812280013,
AI-183.4588.61.34.5202479, JRE 1.8.0_152-release-1248-b22x64 JetBrains s.r.o, OS Mac OS X(x86_64) v10.14.3, screens 5120x1440
Android Gradle Plugin: 3.4.0-beta01
Gradle: 5.1
NDK: from local.properties: (not specified); latest from SDK: (not found);
LLDB: pinned revision 3.1 not found; latest from SDK: (package not found);
CMake: from local.properties: (not specified); latest from SDK: (not found); from PATH: (not found);
Source: user_sentiment_feedback
IMPORTANT: Please read