After the last update of samba app the shares stopped working

My YunoHost server

Hardware: PC
YunoHost version: 11.2.30
I have access to my server : Through SSH | through the webadmin
Are you in a special context or did you perform some particular tweaking on your YunoHost instance ? : no
If yes, please explain:
**If your request is related to an app, specify its name and version: samba 4.13.13~ynh3

Description of my issue

After the last update of samba app the shares stopped working.
I uninstalled and reinstalled the application.
When I tried to create a new share (test) I got an error. The log is here: https://paste.yunohost.org/raw/gicarapufi

From the client machine with smbmap I can get a list of share with "NO ACCESS" for permission (share was created by default at installation, test is the share I tried to create):

cristian@ws:~$ smbmap -H hda
[+] IP: hda:445iName: unknown                                           
        Disk                                            Permissions	Comment
	----                                                -----------	    -------
	share                                             	NO ACCESS	share
	test                                                NO ACCESS	test
	IPC$ 

From smbclient I get:

cristian@ws:~$ smbclient -L hda
Password for [WORKGROUP\cristian]:

	Sharename       Type      Comment
	---------       ----      -------
	share           Disk      share
	test            Disk      test
	IPC$            IPC       IPC Service (Samba 4.13.13-Debian)
SMB1 disabled -- no workgroup available

And when trying to access the share:

cristian@ws:~$ smbclient //hda/share -U samba
Password for [WORKGROUP\samba]:
tree connect failed: NT_STATUS_ACCESS_DENIED
cristian@ws:~$ smbclient //hda/test -U samba
Password for [WORKGROUP\samba]:
tree connect failed: NT_STATUS_ACCESS_DENIED

A temporary solution was to redo everything manually: smb.conf, directories permissions, users’ groups, setting samba password.
I am not savvy enough to understand what’s wrong with the yunohost script(s) or at least witch script creates the problem…