On some platforms and in certain scenarios, when a resource pack is installed as a zip archive, it remains in this state. Currently, if directory names in the zip archive conflict with the filenames of resources referenced from another pack, such as the vanilla resources, Minecraft attempts to load the directory as a resource rather than the actual resource file within another resource pack.

I have provided an example that uses the iron golem. The attached pack contains only a manifest file and a directory duplicating the irongolem texture,"textures/entity/iron_golem". To reproduce:

1. Place the pack "directory_conflicts.zip" in the "resource_packs" directory
2. Start the client and create a world with the given resource pack
3. Observe a content log error for the iron golem texture, and further confirm by spawning an iron golem and noting the missing texture
4. Delete the world, stop the client, and decompress "directory_conflicts.zip" in the "resource_packs" folder, being sure to remove "directory_conflicts.zip" as well
5. Repeat steps 2 and 3, observing there is no longer an issue with the iron golem texture

I believe that this behavior only occurs if the pack is manually placed in the "resource_packs" folder, as most platforms seem to decompress the pack on install. Some platforms also seem to decompress the pack when it is actually placed in the world folder on world creation, though I did not observe this behavior on Android or Windows 10.