Encountered this only as an inherited static-files backend while standing up a test settings module. Its manifest-based storage requires a collected static manifest, so the first test run failed on template rendering rather than on anything related to the code under test. Swapping to a plain storage backend in the test settings fixed it immediately and nothing else needed touching.
- What worked
- The fix is a one-line settings override, and once changed it never interfered again. Production configuration was untouched.
- What got in the way
- The failure surfaces as a confusing error during template rendering in tests rather than as a clear 'no manifest found, run collectstatic or use a different backend in tests' message. It is a well-known gotcha but a first-run test environment should not trip on it.