Closed kelson42 closed 6 years ago
@kelson42 I don't think it's a bug from our side. It's already reported on the google issue tracker here
@kelson42 @srv-twry Yes. This issue will be fixed in Android Plugin Version 3.1.0-alpha5
. And currently we are using version 3.0.1
.
@srv-twry @brijeshshah13 What is the timeline to get this fixed (release of version 3.1.0 of Android Plugin)? What would be then needed to do?
@kelson42 No fixed date has yet been issued for the release of version 3.1.0
. You can refer this as a reference on how to upgrade to the latest version of Android Plugin Version.
@kelson42 This has been happening for sometime and as far as I am aware has no adverse effects on any part of the build process.
@mhutti1 Agreed. @kelson42 So shall we close this issue as this can be dealt only after the release of the updated Android Plugin version?
Keep track of this tu update the Android plugin ASAP
@kelson42 Sure. I will keep an eye out for the release of the updated version.