I've experienced this issue for some time. It's not a blocker but it is a bit annoying.
Steps to reproduce:
Select a region that you want to extract into YASnippet snippet("foo bar").
Eval yas-new-snippet
.
You are redirected to a new buffer +new-snippet+ with the following content:
# -*- mode: snippet -*-
# name:
# key:
# --
// foo bar
// foo bar
Expected behavior:
# -*- mode: snippet -*-
# name:
# key:
# --
// foo bar
pkg-info-package-version yasnippet 20200604.246
edebug-defun
functionyas-new-snippet
to find the reasons. On my configyas-new-snippet
is working like expected.trace-function
the function you suspect being running twice, should be easier than learning how to debug (which I never learned myself)