Can not open links in mobile simulator

[ErikKalkoken]

Checklist

• I have searched the issue tracker for open issues that relate to the same problem, before opening a new one.
• This issue only relates to a single bug. I will open new issues for any other problems.

Describe the bug

We are running a Fyne app in the mobile simulator. When clicking on a hyperlink widget to open an URL in the browser the following error message is shown, but the link never opens:

2025/01/21 01:39:16 Fyne error:  Failed to open url
2025/01/21 01:39:16   Cause: Unable to open url for unknown operating system
2025/01/21 01:39:16   At: /home/erik/go/pkg/mod/fyne.io/fyne/[email protected]/widget/hyperlink.go:257

This error occurs with both widget.NewHyperLink() and when using app.OpenURL().

How to reproduce

1. Run the app in the mobile simulator: go run -tags mobile .
2. Click on the link

Screenshots

No response

Example code

package main

import (
	"net/url"

	"fyne.io/fyne/v2/app"
	"fyne.io/fyne/v2/widget"
)

func main() {
	a := app.New()
	w := a.NewWindow("HBox Experiment")
	u, _ := url.Parse("https://www.google.com")
	w.SetContent(widget.NewHyperlink("Google", u))
	w.ShowAndRun()
}

Fyne version

v2.5.3

Go compiler version

1.23.4

Operating system and version

Ubuntu 22.04

Additional Information

No response

[Jacalz]

The mobile simulator is missing a few features like this, file pickers and keyboard support. Most of it will likely be solved by implementing #5404 but I have an idea for how to easily fix this in the meantime.

[ErikKalkoken]

Thank you. That would be awesome.

For context: The reason this issue is important for me is that my app uses OAuth to authenticate users and it would be very helpful to be able to test the OAuth workflow in the simulator.

[Jacalz]

No problem. I have it on my list to do. That list is however getting rather long so I can't promise any timeline.

[andydotxyz]

You could run the app as a desktop app instead of simulating mobile?

[ErikKalkoken]

You could run the app as a desktop app instead of simulating mobile?

Not really.

I am adding a mobile version to a desktop app, and it will have a custom UI. I am mainly testing the new mobile UI at this point, which will render correctly in the simulator only. But I can deploy the app on Waydroid to test this part of the app, so it is not a blocker.