Problem tying to reset the state machine

[santomegonzalo]

Hi! I'm pretty new to this library and so far I love it... It is solving so many of our issues.

We are currently using @xstate/react with the context because we need the state machine always to be running. The problem is when I'm trying to reset the state machine to go back to the initial state because it is not working as expected.

Some context:

We are using

const actorRef = PaymentContext.useActorRef();
const currentState = PaymentContext.useSelector((s) => s.value);

To get the current state, the machine defines what screen we are showing (we are using react-native).

Simplified example of a machine:

on: {
  reset: {
    target: '.IDLE',
    actions: assign(() => initialContext)
  }
},
states: {
  IDLE: {
    on: {
      start: {
        .......
      }
   }
   ....
}

Now, when we finish our state machine, a user presses a button, and then we send the event reset and I'm seeing the following logs:

 LOG  ========= @xstate.event =========
 LOG  undefined
 LOG  {"id": "x:5", "xstate$$type": 1}
 LOG  {"type": "reset"}

using:

const PaymentContext = createActorContext(machine, {
  inspect: (inspectionEvent) => {
    if (inspectionEvent.type === '@xstate.actor') {
      console.log('========= @xstate.actor =========');
      console.log(inspectionEvent.actorRef);
    }

    if (inspectionEvent.type === '@xstate.event') {
      console.log('========= @xstate.event =========');
      console.log(inspectionEvent.sourceRef);
      console.log(inspectionEvent.actorRef);
      console.log(inspectionEvent.event);
    }

    if (inspectionEvent.type === '@xstate.snapshot') {
      console.log('========= @xstate.snapshot =========');
      console.log(inspectionEvent.actorRef);
      console.log(inspectionEvent.event);
      console.log(inspectionEvent.snapshot);
    }
  },
});

and the next time a user needs to work with the state machine, the machine returns the last visited state instead of IDLE.

I'm a little lost and will appreciate the help.

[santomegonzalo]

I can even see that my currentState is never being called again... 🤔 (it is using the useSelector)... and when I navigate to the reset event I should see my screen changing to wherever I was showing for IDLE state.

[santomegonzalo]

I just created the following repository, where you can see it is not doing what it was expected to do https://github.com/santomegonzalo/xstate-reset-example

Mar-25-2024.11-49-07.mp4

[santomegonzalo]

is this issue happening because my state machine reached the finite state? 🤔