[BUG] - Sometimes doesn't open browswer

[KSanders7070]

There are times when the program will not open the browser when I click on a button that is suppose to open a browser such as the FAQ or ROADMAP buttons.

Attached are two files are from just now when it was happening.

tasklist.txt
FE-BUDDY_LOG.txt

[KSanders7070]

Closing the program and restarting fixed the issue. But I also quit my browser too, so i am not sure which did it.

Next time I will only close my browser to see. Then I will close the program only.

Then the following time I will close the program only and restart.

Considering this has happened before without any current browser open, I am inclined to believe it is restarting the program that would work.

[Nikolai558]

What is your default browser?

[KSanders7070]

Chrome

[Nikolai558]

I think I may have found a solution to this problem. I can't exactly be sure because I have never had this happen on my computer and I am not able to simulate this issue.

Here is the stack overflow link I think explains the issue the best. (Adding link for record keeping) https://stackoverflow.com/questions/21835891/process-starturl-fails

I have added/fixed this in V1.0.2. If this issue occurs again in V1.0.2, please either re-open this issue or create a new one.

[KSanders7070]

This time, I had just updated FE-Buddy. I did NOT restart FE-Buddy. The entire time I had a Chrome browser open. When selecting a button to open a browser, it didn't open it until I closed Chrome and allowed FE-Buddy to open it again by pressing Report Issues.

tasklist.txt

[wiggleforlife]

This may not do anything, but I remember replacing the current browser open function with this.
I replaced the browser function with this -

url = url.Replace("&", "^&");
Process.Start(new ProcessStartInfo("cmd", $"/c start {url}") { CreateNoWindow = true });

You need to import System.Runtime.InteropServices.

If cross-platform stuff is at all a thought, you can

* Check the platform with

RuntimeInformation.IsOSPlatform(OSPlatform.<platform>)

• Use the following to open the browser

LINUX

Process.Start("xdg-open", url);

OS X

Process.Start("open", url);

Again, I have no idea if this will fix anything, it is merely an alternate way of opening the browser.

[Nikolai558]

Is this still a bug in v 2.0.0 or greater?

[Nikolai558]

Due to the lack of activity on this issue, I am going to close it. If this issue continues in 2.1.1 or greater, please feel free to re-open or create a new issue. Thanks.