Bug: Global errors can be caught while restoringSnapshot

[christophe-g]

XState version

XState version 5

Description

I am hitting a problematic scenario in production - yet failing to reproduce in a simple test case.

But basically, this is what I believe is happening:

• For some reasons, restoringSnapshot from persisted layer takes some time (see ability to set `reviveContext` while providing higher-level restoreSnapshot logic #5227 )
• A global error is thrown from an Iframe while restoring state (SecurityError: Blocked a frame with origin from accessing a cross-origin frame) - firebase handling some part of auth stuff
• the Security error is caught here and the machine ends up in an error state

Expected result

I am expecting the machine to end up in an error state only when the context is not able to be restored.

Actual result

Machine ends up in error state when global errors - not related to state restauration - are thrown

Reproduction

sorry, unable to give a simple repro

Additional context

No response

[davidkpiano]

The best way for me to debug this is with a repro; is there any way to create a repro for even part of the problem so we can work off something?

[christophe-g]

The best way for me to debug this is with a repro;

Yes I know, sorry. It has been hell just to identify the cause of this.

I'll try to deploy a unminified version somewhere and (hopefully) steps to reproduce.

[christophe-g]

@davidkpiano - DMed you to the address linked to your profile

[christophe-g]

@davidkpiano - I published a new preview to a new preview channel as the old one has expired. Links sent to your email address.

[davidkpiano]

Apologies for the delay - this is a tricky one to debug without a simple reproduction.

Is there a way for you to trigger some global error during restoration in a simpler reproduction?