I don't have reproducible steps, apologies. But here's what happened:

I was demoing https://bgfetch-http203.glitch.me/, which included initiating a podcast download in Chrome Canary on Android with the Experimental Web Platform features enabled, and terminating Chrome while the download was ongoing (as background fetch will continue the download).

When I returned to the app, it failed to show podcasts.

Turns out the XML feed for the podcasts had only partially cached. https://gist.github.com/jakearchibald/7b0b2afd434d780eb605d73c9e59c409 - this was what was in my cache vs what comes from the network.

https://glitch.com/edit/#!/bgfetch-http203?path=public/client.js:279:0 - Here's where the feed is cached. It's just fetching, then using cache.put.

Because I was closing Chrome (by swiping Chrome away in Androids app switcher), it feels like I've interrupted it during writing. Ideally it shouldn't allow a partial write like this.

Again, sorry I don't have proper recreation steps.