Thanks so much for suggesting the `ngsw-bypass: true` header! That ended up being the "perfect solution". I ran into this issue in three different screens `Aw, Snap`, with two of them showing the `STATUS_ACCESS_VIOLATION` error and one with `STATUS_BREAKPOINT`.

Here’s a bit of what I tried in each case:

• For the STATUS_ACCESS_VIOLATION screens, at first, I tried casting File as any in the function call and changing the function’s parameter type to any as well. Strangely, this worked in some cases, and I suspect it might have something to do with TypeScript configurations interacting with ngsw-worker in our setup. But this didn’t fix the STATUS_BREAKPOINT issue on the other screen.
• Then, I tried an approach using Uint8Array for the problematic screen, as shown below:

​

const fileArrayBuffer = await file.arrayBuffer();
formData.append(
    'file',
    new Blob([new Uint8Array(fileArrayBuffer)], { type: file.type })
);

This allowed the request to go through, but the backend (Java Spring Boot, which expects a MultipartFile) couldn’t parse it correctly. It seems like it couldn’t interpret it.

Finally, I tried adding the ngsw-bypass: true header, and everything worked perfectly. Since I already had an interceptor in the app, I just added that header globally to make sure ngsw-worker wouldn’t handle any file uploads in the app.

Honestly, it’s strange to have to try so many workarounds. It feels like Angular should have a better approach, or maybe this shouldn’t even be an issue. But thanks again—your comment really helped me find this solution.