Opening a link in Orion profile through the Orion app opens the wrong profile / doesn't open the link

I'm hitting the same issue... I'll include my comment / findings that I mentioned in Discord here: https://discord.com/channels/802933355603034132/802933355603034135/1222326853713268820

this open command I'd have thought would work:

open -a ~/Applications/Orion\ RC/Orion\ RC\ Profiles/D4C4613B-F6B9-450A-8069-46AE247BDEF0/Orion\ RC\ -\ <PROFILENAME>.app https://google.com

given that this works for the default profile:

open -a /Applications/Orion\ RC.app https://google.com

In the case where I'm launching the profile's .app - I see the app icon for the appropiate profile appear briefly in the dock but then it quits and re-launches the default profile.

Thanks @eskidostlar - I'll downgrade to 126.4.1.

dino I appreciate the response however I cannot get that to work... tested with 127.1.

I'll attach a screen recording of my issue. My Red Profile is the default and the green profile is the ID I'm using in the open commands. I've also aligned the profile colors with the background of the NTP.

You'll see that the provided profile ID is ignored - Orion honors the setting "Open external links in".

Same issue is present in 0.99.127.2. wasn't expecting a fix as it wasn't in the changelog but thought it'd be good to keep this up to date.

@Vlad I don't believe we can close this issue - I've just tested with 0.99.127.2.2-rc (WebKit 619.1.1) and I can still reproduce the issue with the steps above.

dino I'm still able to recreate the issue mentioned in the post (as well as my previous comments).

I'm doing the following steps:

1. Open 2 profiles - the default profile and a custom profile I've setup (in Version 0.99.127.2.2-rc (WebKit 619.1.1))

2. When the default profile was last used, opening a link with Choosy (or a terminal command with the profile specified) for the custom profile opens in the default profile. This is point 1 in the post.

3. If I then close all windows for both profiles, closing the custom profile first and then the default profile second. Opening a link for the custom profile with Choosy or Terminal commands opens a new window of the default profile with the link intended for the custom profile. This is point 2 in the post.

LachlanGrant so basically the issue is, when you are specifing profile-id in terminal or choosy, it's ignoring that and opening link in last active profile. correct? so your request is to consider profile-id too for prioritizing profile when opening links?

LachlanGrant thats because the app didn't get extra arguments sent to a running instance, only URL is accessible directly, so we are still checking for a solution for accessing other args on runtime.

And the main post is about a regression where "Open external link in" is getting ignored, thats why we needed to mark this done. So I will request you to create a new feedback post with the details, as multiple different requests can't be tracked with single bug (as it's completely confusing for us and other users too).

eskidostlar Not sure if you are saying this is not fixed in 127.2 or just refering because the post is not about Open external links in: behaviuor? Just to clarify, that both issues are due to same regression, and the issue was due to incorrect handling of Open external links in:, and thats why I referred that.

But if the issue still reproducible, can you please share more context with your points, as some of the things are not clear to me here:

1- I have a window with profile A, don't have any apps/windows with profile B, and click on a link that should open in profile B (hence forwarding the link to the separate app that Orion creates for profile B). The link opens in profile A.

You mean Profile A is running and have a window open. and you also have Profile B, but you closed all windows.
Now its not clear, that from where you are clicking the link. Let you clicked from any X external app, how you are so specific that the link should be open in Profile B? it will based on Open external links in: Preference under General tab. And this what happens now in latest RC (127.2.2), however you might be using 127.2 beta, so the behaviour can be different, So will mark this as "Next Release" for more clarity

And if you are refering to Orion Web App created for specific target profile, it's working fine in 127.2 release. If you still have different behaviour, please share a recorded video.

2- I have no Orion apps/profiles running. The last profile I used is profile A. I click on a link that should open in profile B (hence forwarding the link to the separate app that Orion creates for profile B). An empty window for profile A launches. It doesn't navigate to the clicked link.

Same for this, as this also working fine in beta 127.2

I just tried to reproduce this issue, and see the same behaviors, that the --args -P don't really do much.

I have tried it on the version Version 0.99.130.2-beta (WebKit 621.1.2.111.4)

If I don't have any windows open - this command works, it can open a specific profile. But if one of the windows is already opened - all links are going to go there.

To reproduce is:

1. Download fresh version of the browser.
2. Create second profile, I called it Work.
3. Get the GUID of the "work" profile. Close all the windows.
4. In terminal run (one by one)

open -a /Applications/Orion.app https://google.com --args -P 34E33AD7-A788-4523-9572-B5E2FF40CC1C
open -a /Applications/Orion.app https://google.com --args -P Default

Where 34E33AD7-A788-4523-9572-B5E2FF40CC1C is your own GUID for the profile ID.

Both links are going to be sent to the same profile window. Where I expect to see links to be opened in Work and Default profile respectfully.

outcoldman I suggest opening a new bug report with exact steps to reproduce and refernecing this.