Thanks! as you suggested, it appears to be a bug related to macOS 14 (was on beta 5 and got the same result). It worked on 13.5.