IssueTracker

Weird, I can't reproduce that (see screenshot). Note that lint does cache the database of versions downloaded from maven.google.com for roughly 7 days, but given how the version you're using is quite a bit older than the current version that doesn't seem like it's the problem.

I have never seen that BOM's are suggested updated anytime, anywhere... ... I'll try to keep my eyes open and check the maven repository every day (or somewhat), is it enough with the IDEA log file, to pinpoint the problem ?

Can i tweak the lint cache time to 0 days (1 day ?)?, and is that the reason for the difference I see between gradle (lint check), maven repository and project structure (https://issuetracker.google.com/issues/190075875)?

Didn't discover BOM rise from 28.2.0 -> 28.2.1 either

See picture, attaching log.

I see also (norwegian) error messages which translates into "An existing connection was forcibly shut down by the external host", that might be something to watch out for in the logs.

Still a problem in 2021.1.1.5, see picture.

Attaching logs.

Thanks for the report. I've committed a fix for the Project Structure, and from the first Canary of the next Android Studio series the Suggestions tab of the Project Structure Dialog will suggest an upgrade to platform dependencies such as the Firebase BOM. I or someone else will update this bug as and when lint is changed to also detect this, and to show highlighting in the Gradle build file.

BTW, I've submitted an issue about Lint support for BOM a year ago.

We've now submitted a fix for Lint to highlight outdated platform dependencies in Gradle build files, which should be available in a forthcoming Android Studio Iguana pre-release. Thanks once again for the report.

Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:

• Android Studio Iguana | 2023.2.1 Canary 17
• Android Gradle Plugin 8.3.0-alpha17

We encourage you to try the latest update.

If you notice further issues or have questions, please file a new bug report.

Thank you for taking the time to submit feedback — we really appreciate it!