As others wrote, there is no information, so I can only answer the problem at the level I expected, but wouldn't it be solved by updating the Gem using listen?
Perhaps the problem is not listen itself.For example, if the guard or something depends on listen and there is an inconsistency in those versions, you will get an error similar to the one above.
It may be possible to resolve this issue.For the part that corresponds to the guard, please check Gemfile.lock for the gem that uses listen.
© 2022 OneMinuteCode. All rights reserved.