The issue you're encountering seems to be related to the interaction between the eventMode property and the setSkin function in the @pixi/spine-pixi runtime. The error message indicates that there is a problem with the batcher property, which is likely related to the rendering pipeline of the spine object when the skin is changed.

Here are a few steps you can take to troubleshoot and potentially resolve the issue:

1. Ensure Proper Initialization: Make sure that the spine object and its skeleton are properly initialized before setting the skin or adding interactivity.

2. Check for Null References: Before setting the skin, ensure that all necessary properties and objects are not null or undefined. This includes the spineObject, skeletonData, and any skins you are trying to add.

3. Update Renderable State: After setting the skin, you might need to update the renderable state of the spine object to ensure that it is correctly rendered with the new skin. This can be done by calling the update method on the spine object or forcing a re-render.

4. Event Mode and Skin Change: Since the error occurs when eventMode is set, try temporarily disabling the event mode before changing the skin and re-enabling it afterward. This can help isolate whether the issue is directly related to the event mode.

Here is an updated version of your setSkin function with additional checks and steps:

const setSkin = () => {
  if (!spineObject || !skeletonData) {
    console.error('Spine object or skeleton data is not initialized.');
    return;
  }

  // Temporarily disable event mode
  const previousEventMode = spineObject.eventMode;
  spineObject.eventMode = 'none';

  const skin = new Skin('custom');
  const baseSkin = skeletonData.findSkin('skin-base');
  if (baseSkin) {
    skin.addSkin(baseSkin);
  } else {
    console.error('Base skin not found.');
  }

  groupedSkins.forEach((skinGroup) => {
    const skinName = skinGroup[getRandomInt(0, skinGroup.length - 1)];
    const foundSkin = skeletonData.findSkin(skinName);
    if (foundSkin) {
      skin.addSkin(foundSkin);
    } else {
      console.error(`Skin ${skinName} not found.`);
    }
  });

  spineObject.skeleton.setSkin(skin);
  spineObject.skeleton.setSlotsToSetupPose();

  // Re-enable event mode
  spineObject.eventMode = previousEventMode;

  // Force update renderable state
  spineObject.update(0);
};

Additionally, ensure that your event listener setup is correct:

spineObject.eventMode = 'dynamic';
spineObject.on('pointerdown', () => {
  spineObject.state.setAnimation(1, 'blink', false);
  spineObject.state.setAnimation(2, 'aware', false);
  spineObject.state.addEmptyAnimation(2, 0.2, 0);
});

If the issue persists, it might be worth checking if there are any known issues or updates related to the @pixi/spine-pixi runtime and the specific version of Pixi.js you are using. You can also consider reaching out to the maintainers of the @pixi/spine-pixi package for further assistance.

In general, by calling state.update(0), you force the skeleton to re-evaluate its current state, ensuring that all attachments and constraints are correctly set according to the new skin.

The crash might be related to the fact that some attachments are not yet set in the skeleton and Pixi is trying to render something that does not exist.