Hey folks,
We have now reproduced this issue and are looking into a fix. It doesn’t appear that downgrading and upgrading is a workaround at this point. We have confirmed that reverting back to the previous version does cause the issue to go away. We recommend that people who experience this issue stay on the 2.2.2 firmware version if they want to use FX.