cli issues : env.uglify breaks console.log / hmr / debugger cannot connect device

Environment
✔ Component nativescript has 7.0.11 version and is up to date.
✔ Component @nativescript/core has 7.0.12 version and is up to date.
✔ Component @nativescript/ios has 7.0.4 version and is up to date.
✔ Component @nativescript/android has 7.0.1 version and is up to date.
✔ Xcode version 12.1.0 satisfies minimum required version 10.

Describe the bug
I have several issues when deploying the app
Using the emulator :

1. when I use the --env.uglify flag, console.log messages are not shown in the console.
2. when I have HMR active, the app closes after it launched. I have to manually start it to use it.
3. navigating to devtools://devtools/bundled/inspector.html?ws=localhost:41000 gives a timeout :
   Cannot connect to device socket. The error message is 'Timeout while waiting for lock "/Users//.local/share/.nativescript-cli/abb5c8da9f657a0090e2668a3a72a99b"'.
   NativeScript debugger was not able to get inspector socket port on device 6F98B19F-AC48-4CE6-917C-590F22F2559B for application org.nativescript.foo.
   Cannot connect to device socket. The error message is 'Device socket port cannot be found.'.

To Reproduce

• create a new ns Angular project with ns create foo --ng
• open items.component.ts and add the line console.log('NS rules!'); to ngOnInit
• run the project with : ns debug ios --> You see the added log message
• run the project with : ns debug ios --env.uglify
  1. the app closes after it is started --> not correct
  2. start the app yourself manually, notice you don't see the added log message --> not correct
• run the project with : ns debug ios --env.uglify --no-hmr --> the app does not close after it starts correct
• navigate to devtools://devtools/bundled/inspector.html?ws=localhost:41000

Sample project
See 'To Reproduce'

Commencez par reproduire le comportement avec ns debug ios, --env.uglify et --no-hmr, en utilisant le console.log ajouté à items.component.ts. Examinez ensuite les points d’entrée de la CLI impliqués dans HMR, l’uglification et la connexion du débogueur à l’URL de l’inspecteur. C’est terminé lorsque les exécutions uglifiées conservent la sortie de la console, que HMR ne ferme pas l’application et que le débogueur se connecte à l’appareil.