IssueTracker

Artifact used (ex. androidx.appcompat:appcompat:1.0.0-alpha1): workmanager 2.5.0, AGP 7.0.0 with checkDependencies enabled Version used: see above Theme used: N/A Devices/Android versions reproduced on: N/A build only

We have a multimodule project that looks like this:

// Main apk project where lint is run from
app/src/main/AndroidManifest.xml

// app-legacy subproject where Application subclass lives
apps/app-legacy/src/main/.../SlackAppDelegate.kt, interface that extends Configuration.Provider
apps/app-legacy/src/main/.../SlackApp.java, Application subtype that implements SlackAppDelegate

// Service subproject that contains workmanager code. Its manifest declares the tools:node="remove" element
services/work-manager/src/main/AndroidManifest.xml

With this structure, the RemoveWorkManagerInitializer lint reports the manifest in apps/app-legacy/src/main/AndroidManifest.xml as needing to remove it, even though it should be there in the merged manifest from the service project.

This is what we have in the service manifest

<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
    xmlns:tools="http://schemas.android.com/tools"
    package="slack.workmanager">
    <application>
        <provider
            android:name="androidx.work.impl.WorkManagerInitializer"
            android:authorities="${applicationId}.workmanager-init"
            android:exported="false"
            tools:node="remove" />
    </application>
</manifest>

I do also see this provider in the merged manifest in app-legacy's intermediate outputs

<provider
            android:name="androidx.work.impl.WorkManagerInitializer"
            android:authorities="${applicationId}.workmanager-init"
            android:exported="false"
            tools:node="remove" />

This only started with AGP 7 and when we switched to checkDependencies = true