This is caused by OSX Catalina (and possibly earlier OSX releases) removing the execution flag from the internals of the launcher.app.

It is resolved as per the following video ...


https://youtu.be/i9TtoOJjGpU


On thing to note - quite a few customers are forgetting to put a space after the "chmod +x" command in the video. This causes the command to fail. Please make sure you type a space after chmod +x and the command should then run ok.