RTK errors are swallowed (no log, no report)

[fregante]

Repro:

1. Add throw new Error('TEST') to after the UUID line

   pixiebrix-extension/src/pageEditor/tabState/tabStateSlice.ts

   Lines 49 to 54 in 4061afe

   	const connectToContentScript = createAsyncThunk<
   	FrameConnectionState,
   	void,
   	{ state: TabStateRootState }
   	>("tabState/connectToContentScript", async (arg, thunkAPI) => {
   	const uuid = uuidv4();

2. Open the console or background console

The error is never reported, it doesn't bubble up to the global handler nor there's any RTK-specific handler to catch it. It's completely hidden from the developer.

In this case it appears in the UI, but I suppose it might as well not:

Related

• Review error handling in RTK #4032

[twschiller]

Raising priority of this in case it's the root cause of missing error indicators in other places

[corinnemayans]

Story points: 2

[BLoe]

@twschiller What does "missing error indicators in other places" refer to here?

[fregante]

Probably: since errors are swallowed, it's possible that they're not being displayed anywhere even in the UI. The screenshots above do show this "error indicator" but other places might not.

[twschiller]

@twschiller What does "missing error indicators in other places" refer to here?

Correct, I was just flagging that it could cause user error toasts/form validation to not appear in some places. I didn't not investigate particular cases.