MacOS Big Sur Terminal command ‘open’ behaviour changed and I don’t know how to get back to how it was in Catalina

big surmacosterminal

I updated my macOS to Big Sur 11.0.1 and it seems that they changed the way open command or rather launch services are acting in this version.

I have different versions/releases of my software on my machine in separate folders. Name of my .app is some-app.app (example). If I run this app with open some-app.app then this works perfectly fine and runs my application.

Now if I navigate my Terminal to a different folder with the same .app name and I try to use same command it is actually going to bring up the existing one already running. This is incorrect as this is 2 different instances of app.

I tried renaming one of them thinking this might have something to do with it but no luck, it still brings up already open application.

Please note that I have also checked the process COMMAND by using ps aux and the command of the first app is clearly pointing to correct folder and correct name – which is different then the second instance that I'm trying to run.

I'm also aware of the fact that I could run my app from Contents/MacOS folder inside the package but that is not the solution I am looking for.

Any ideas what could have changed from Catalina that this is happening?

Best Answer

For now it seems that open -n someapp.app was the solution. I'm not sure if I will run into issues later down the line where I'm not able to use this command but it works at the moment.

Thank you @nohillside for the idea.

UPDATE: What I've done is alias open="open -n" and it seems so far that this is now working same as it was working pre-Big Sur :)