Fixed
Status Update
Comments
am...@google.com <am...@google.com>
tn...@google.com <tn...@google.com> #2
This is per design; in order to know if a user has the Chromecast extension installed (and which one), cast_sender.js requests the script from all potentially installed extensions.
tn...@google.com <tn...@google.com> #4
This is amateurish at best, incompetent at worst. It's bad and Chrome developers should feel bad.
tn...@google.com <tn...@google.com> #5
at least keep the console free of errors...
to...@yahoo.com <to...@yahoo.com> #6
likely related:
Objects.requireNonNullElse
Objects.requireNonNullElseGet
are now also showing this same false positive warning.
Android Studio Koala | 2023.3.2 Canary 2 gradle 8.6 plugin: 8.3.1
tn...@google.com <tn...@google.com> #7
This would be about 3 lines of code to fix. I'm very surprised Chromecast team considers it reasonable to dump a long list of error messages in the vast majority of people's browsers, ie > 99% of users of a typical web app are either using another browser or using Chrome but without Chromecast, and this will aversely affect all of them.
"Don’t leave “broken windows” (bad designs, wrong decisions, or poor code) unrepaired. Fix each one as soon as it is discovered." [1]. By routinely dumping error messages in almost everyone's consoles as if it were a normal situation, you are encouraging developers and users to ignore error messages instead of taking them seriously, as they should do, and you are making it impossible for developers to attain a pristine error log.
1.https://pragprog.com/the-pragmatic-programmer/extracts/software-entropy
"Don’t leave “broken windows” (bad designs, wrong decisions, or poor code) unrepaired. Fix each one as soon as it is discovered." [1]. By routinely dumping error messages in almost everyone's consoles as if it were a normal situation, you are encouraging developers and users to ignore error messages instead of taking them seriously, as they should do, and you are making it impossible for developers to attain a pristine error log.
1.
to...@yahoo.com <to...@yahoo.com> #8
This is ridiculous and very annoying. I dont want to see this error every time when developing.
Please fix!
Please fix!
tn...@google.com <tn...@google.com> #9
Agree with all comments above. Please fix!
to...@yahoo.com <to...@yahoo.com> #10
Very annoying for me too. Trying to fix a bug in a program and it took me a while to figure out that this wasn't part of the bug and wasn't something I was doing.
sg...@google.com <sg...@google.com> #11
yeah amateurish at best. should fix!
tn...@google.com <tn...@google.com> #12
I have not installed cast sender yet I'm seeing errors in my chrome dev console. not good.
tn...@google.com <tn...@google.com> #13
Completely ridiculous. It's a simple fix. Fix it.
to...@yahoo.com <to...@yahoo.com> #14
How is this a wontfix? What the heck you guys? Are you expecting patch requests for it if someone else tackles it?
gh...@google.com <gh...@google.com> #15
[Comment deleted]
sg...@google.com <sg...@google.com> #16
I guess we should all leave the Google community and go back to Firefox then...
sg...@google.com <sg...@google.com> #17
Do any of you guys create apps ? e.g. I have created one in the past and noticed that within my Eclipse environment, i have downloaded the 'Google Play services API' as part of a project. This enables (amongst other things) 'Google Cast'.
Wondering if this could be part of the reason I'm seeing the cast_sender.js issues ? or am I clutching at straws....
Wondering if this could be part of the reason I'm seeing the cast_sender.js issues ? or am I clutching at straws....
to...@yahoo.com <to...@yahoo.com> #18
Jon - that's right, there's no mystery here. I assume Eclipse's "Google Cast" will cause your app to link to include the official cast_sender.js script, and that script is broken as it insists on trying to fetch a resource that will only be present if users are in Chrome and Chromecast extension is installed. Otherwise, it will dump errors.
tn...@google.com <tn...@google.com> #19
Annoying!
tn...@google.com <tn...@google.com> #20
So what, send the requests to detect Chromecast extensions.
*Don't pollute the console.* That's entirely different.
*Don't pollute the console.* That's entirely different.
sg...@google.com <sg...@google.com> #21
I think there's something called a try-catch block or something?
tn...@google.com <tn...@google.com> #22
this has been more than 4 months and no one is bothering to reply form the development team. It very annoying for me see those error line every time i look at the console. Please fix it.
sp...@google.com <sp...@google.com> #23
Is it possible this is affecting Analytics tracking? My Chrome direct traffic suddenly dropped on 4th October 2014 without any apparent reason.
Thanks
Thanks
bi...@google.com <bi...@google.com>
an...@google.com <an...@google.com> #25
i'm really puzzled with the attitude towards this issue :/
to...@yahoo.com <to...@yahoo.com> #26
This is a serious issue and interferes with all chrome based web development as well as driving developers, like myself, away from using chrome. Please fix this ASAP!
Description
Lint shows NewApi warnings in Android Studio despite using coreLibraryDesugaring in the main application module. I followed the official documentation for adding desugaring, but it shows the errors both an existing multi-module project and a newly created single module project.
The API I tested with was ArrayList#removeIf(..).
It does show the warning:
- for JVM target 8, 11 and 17
- in java as well as in kotlin classes
- for single module projects as well as for multi module projects
I made sure the desugaring was actually working by building the app without it. It crashes to 21 WITHOUT the library enabled. It does NOT crash on 21 WITH the library enabled, but the warning is still there.
I attached a demo project as zip.
STEPS TO REPRODUCE:
1. Create a new Project with Android Studio.
2. Add coreLibraryDesugaring as written down in
3. Call ArrayList<..>().removeIf(..).
ATTACH SCREENSHOTS/RECORDINGS OF THE ISSUE
-
ATTACH LOG FILES (Select Help > Show Log in Files, or Show Log in Finder on a Mac)
-
------------------
IMPORTANT: Please read
all required information.
------------------
Studio Build: Iguana | 2023.2.1 / Build #AI-232.10227.8.2321.11479570, built on February 21, 2024
Version of Gradle Plugin: 8.3
Version of Gradle: 8.4
Version of Java: 17
OS: Windows 11