When I try to add a Google account to an app like Fantastical, the oAuth link results in a 400 Error when Choosy is used to pass the URL to the browser.

For example, when using Choosy to pass the link from Fantastical to Safari, the requested URL starts with "https://accounts.google.com/signin/oauth/legacy/consent?authuser=0&part=blahblahblah....."

This URL results in a 400 Error ("The server cannot process the request because it is malformed. It should not be retried. That’s all we know.").

When I disable Choosy, and just have the link open in the default browser, the URL passed looks different. It looks like this:

https://accounts.google.com/o/oauth2/v2/auth/oauthchooseaccount?client_id=bahblahblah.....

This URL, however, works as expected.

When setting up a rule, if the resulting action ends in "...", the interface does not make clear what the user should do to finish the setup process. The simplest way to make the interface clearer would probably be to change the text on the "Change" button to something like "Pick" or "Choose", and perhaps use a placeholder with text like "No browser chosen" where the browser icon and browser name would be once a browser has been chosen.

If you were to redesign the interface a little bit more, it might make sense to make the entire area below the action dropdown be clickable, rather than just the "Change" button, so that the user could click the browser name or placeholder text to get the "Change" menu.

If, for example, I type in a GitHub URL or click on a link in the browser that points to a GitHub URL, and I have Choosy set up to open GitHub URLs in a different browser (such as a single-site browser), it would be nice if the Choosy extension could automatically capture that URL and open it in the specified browser, rather than depending on me clicking the Choosy toolbar icon.

Does this make sense?

Basically, links in the browser should behave like links in, say, Mail, and open in the correct browser rather than just the browser you're already in.

Installed 0.93 over previous version. Each time I click on the pref pane, it tells me Choosy is not enabled. I tick all four boxes in the "enable Choosy" section, click "Start helper now" and press Cmd-Q.

On going back to the pref pane, I am warned about Choosy not being enabled AGAIN. All four boxes are unticked and the helper is shown as not running. (BTW, the first click on Choosy changes the title bar to "Loading Choosy" but the pane does not appear — I have to click it again to get this far)

This happens even if I completely uninstall and reinstall Choosy.

It would be great if you could make FileMaker google oauth play nice with a secondary browser, e.g. Vivaldi. I get as far as getting the rule to work: w.o.w. Vivaldi opens, automatically accepts, FileMaker continues the login... but Vivaldi stays open with the window open as well. And this is exactly the outcome that I want to avoid. After 10 auths there are windows all over the place. It would be nice if the operation works just like the browser is the default browser: if it is not open, it starts, opens the auth window, authenticates, closes the window, quits. The solution might be to include an option in the rule to close the browser after a given number of milliseconds.