title: Disable WorkManager Initializer when using app startup
body: <p>I'm using WorkManager 2.7.1 with Hilt and up till now I've always just removed app startup completely:</p>
  <pre><code>&lt;provider
    android:name=&quot;androidx.startup.InitializationProvider&quot;
    android:authorities=&quot;${applicationId}.androidx-startup&quot;
    tools:node=&quot;remove&quot;&gt;
  &lt;/provider&gt;
  </code></pre>
  <p>I'm now ingesting another library that is actually using app startup so I need to just stop the WorkManager initialisation as per the guidelines <a href="https://developer.android.com/topic/libraries/architecture/workmanager/advanced/custom-configuration" rel="nofollow noreferrer">here</a></p>
  <pre><code>&lt;provider
    android:name=&quot;androidx.startup.InitializationProvider&quot;
    android:authorities=&quot;${applicationId}.androidx-startup&quot;
    android:exported=&quot;false&quot;
    tools:node=&quot;merge&quot;&gt;
    &lt;!-- If you are using androidx.startup to initialize other components --&gt;
    &lt;meta-data
      android:name=&quot;androidx.work.WorkManagerInitializer&quot;
      android:value=&quot;androidx.startup&quot;
      tools:node=&quot;remove&quot; /&gt;
  &lt;/provider&gt;
  </code></pre>
  <p>Unfortunately, however, I'm not sure this is actually doing what it's supposed to. I get errors whenever I try to access a Worker in the same way that I would get in the previous configuration if I missed out the removal of <code>InitializationProvider</code>. So is the documentation correct or is it just not valid for the latest WorkManager?</p>
  <p>I have observed that the log from WorkManagerInitializer <code>Initializing WorkManager with default configuration.</code> does not happen with either of the options but for whatever reason Hilt is no longer creating the classes referenced by @HiltWorker</p>