Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Dagger 2.27 and lint compliance

See original GitHub issue

In our multi-module project, we are using dagger 2.27

implementation 'com.google.dagger:dagger-android:2.27'

and just this morning I noticed a lint compliance error for this version and asked me to update to 2.35.1

 This version is . Details: Consider switching to recommended version 2.35.1.

I’m trying to find out what could have triggered this compliance error just now since all other versions remained the same.

Issue Analytics

State:
Created 2 years ago
Reactions:6
Comments:5 (1 by maintainers)

Top GitHub Comments

1reaction

arekolekcommented, May 12, 2021

@anilgorthy Can you post a link here if you report it somewhere else?

0reactions

arekolekcommented, May 21, 2021

I was going to report an issue similar to this one https://issuetracker.google.com/issues/170240589, but I got an error saying “You do not have permission to create issues in this component.”, so I’ll just leave a comment here.

What changed is this metadata file https://dl.google.com/dl/android/sdk/metadata/sdk_registry.xml. It used to say:

  <library  groupId="com.google.dagger" artifactId="dagger-android" recommended-version="2.15" >
    <versions from="2.15" />
    <versions from="2.14.1" status="deprecated" description="Bug affecting SDK performance" url="https://github.com/google/dagger/releases/tag/2.15" />
    <versions from="2.14" status="deprecated" description="Bug affecting SDK performance" url="https://github.com/google/dagger/releases/tag/2.15" />
    <versions from="2.13" status="deprecated" description="Bug affecting app performance" url="https://github.com/google/dagger/releases/tag/2.15" />
    <versions from="2.12" status="deprecated" description="Bug affecting app performance" url="https://github.com/google/dagger/releases/tag/2.15" />
    <versions from="2.11" status="deprecated" description="Bug affecting SDK performance" url="https://github.com/google/dagger/releases/tag/2.15" />
    <versions from="2.11-rc2" status="deprecated" description="Bug affecting SDK performance" url="https://github.com/google/dagger/releases/tag/2.15" />
    <versions from="2.11-rc1" status="deprecated" description="Bug affecting SDK performance" url="https://github.com/google/dagger/releases/tag/2.15" />
    <versions from="2.10" status="deprecated" url="https://github.com/google/dagger/releases/tag/2.15" />
  </library>

And now it says:

  <library  groupId="com.google.dagger" artifactId="dagger-android" recommended-version="2.35.1" >
    <versions from="2.15" />
    <versions from="2.14.1" status="deprecated" description="Bug affecting SDK performance" url="https://github.com/google/dagger/releases/tag/2.15" />
    <versions from="2.14" status="deprecated" description="Bug affecting SDK performance" url="https://github.com/google/dagger/releases/tag/2.15" />
    <versions from="2.13" status="deprecated" description="Bug affecting app performance" url="https://github.com/google/dagger/releases/tag/2.15" />
    <versions from="2.12" status="deprecated" description="Bug affecting app performance" url="https://github.com/google/dagger/releases/tag/2.15" />
    <versions from="2.11" status="deprecated" description="Bug affecting SDK performance" url="https://github.com/google/dagger/releases/tag/2.15" />
    <versions from="2.11-rc2" status="deprecated" description="Bug affecting SDK performance" url="https://github.com/google/dagger/releases/tag/2.15" />
    <versions from="2.11-rc1" status="deprecated" description="Bug affecting SDK performance" url="https://github.com/google/dagger/releases/tag/2.15" />
    <versions from="2.10" status="deprecated" url="https://github.com/google/dagger/releases/tag/2.15" />
  </library>

Not sure if this was a deliberate change, because they didn’t add any status or description for versions 2.15 - 2.35 when raising the recommended-version.

I can only guess it has something to do with Hilt graduating to stable in 2.35?

Top Results From Across the Web

Getting started with Dagger 2.27 on Android by example

equip an existing minimal app with DI; work with the latest Dagger 2 version 2.27; avoid writing boilerplate code.

hilt-android : 2.40.5 - com.google.dagger - Maven Central

A fast dependency injector for Android and Java. ... Dependencies: com.google.dagger:dagger · com.google.dagger:dagger-lint-aar · com.google.dagger:hilt ...

homebrew-core - Homebrew Formulae

a2ps 4.14 Any‑to‑PostScript filter aacgain 1.8 AAC‑supporting version of mp3gain aalib 1.4rc5 Portable ASCII art graphics library aamath 0.3 Renders mathematical expressions as ASCII art

Dagger Lint Rules(2.42) - Javadoc

A fast dependency injector for Android and Java. Group Id, com.google.dagger. Artifact Id, dagger-lint. Version, 2.42. Packaging ...

Lint Fails when using lateinit var inside tests - Issue Tracker

“ aiv dexif ,1023/seussi/reggad/elgoog/moc.buhtig//:sptth si siht eveileb I https://github.com/google/dagger/commit/ ...