Closed this issue 3 months ago · 1 comments
this was noticed during no-login testing
fixed in v2.3.134