title: Caused by android.view.InflateException Binary XML file line #101: Caused by android.content.res.Resources$NotFoundException
body: <p>Got this error from Crashlytics, affecting a few devices:</p>
  
  <p><strong>Caused by android.view.InflateException
  Binary XML file line #101: Binary XML file line #101: Error inflating class </strong></p>
  
  <p><strong>Caused by android.content.res.Resources$NotFoundException
  Drawable (missing name) with resource ID #0x7f06008a</strong></p>
  
  <p>The interesting thing is that this has only come about since I released the app in the new Android App Bundle. This didn't happen when releasing the .apk. In fact to resolve it I reverted back to release it as .apk. But I want to have the benefits of a release with the new Android App Bundle. I know it's something to do with the Drawable folders. Here's line 101 in the xml file:</p>
  
  <pre><code>&lt;ImageView
      android:id="@+id/learn_chords_help_button"
      android:layout_width="wrap_content"
      android:layout_height="wrap_content"
      android:paddingLeft="0dp"
      android:paddingTop="20dp"
      android:src="@drawable/help"
      android:contentDescription="Learn Chords Help"
      android:layout_toRightOf="@id/learn_chords_button"
      android:layout_above="@id/creditText"
      /&gt;
  </code></pre>
  
  <p>Here's all my drawable folders with/without help.png:</p>
  
  <pre><code>drawable -&gt; help.png
  drawable-hdpi -&gt; help.png
  drawable-nodpi -&gt; No Help image
  drawable-xhdpi -&gt; No Help image
  drawable-xxhdpi -&gt; help.png
  </code></pre>
  
  <p>Here's some devices that the error occurred on (according to Crashlytics, I couldn't replicate it with the few test handsets we have): Galaxy J7(2016) 7.0, Optimus L40 4.42, m3 Note 5.1, Galaxy s4 4.4.2)</p>
  
  <p>Is this a bug in the Google Play's new App Bundle format, or do developers need to have all the drawable folders with assets in each of them? </p>