Hi,
This is apparently a xepersian bug. See [1].
[1] https://github.com/tex-xet/xepersian/issues/20
-- Eliad Bagherzadegan (eliad.dev@gmail.com)