OSM Scout (native map app)

Applications
1

While there’s quite a bunch of topics and discussion around Pure maps and OSM Scout server, there seems to be practically none about OSM scout by @karry, which I tend to favour for many usescases.

So, question: What does the message “unsupported url” mean?

2 Likes
2

It is my map app of choice, too. Afaik the message means, that OSM Scout cannot handle the URL (e.g. if you have a “malformed” location entry in your calender and OSM Scout tries to open this).

2 Likes
3

I’m not aware of using any kind of URL, don’t have any referenced calendar entries either. It just appears every time I open the application.

4

I also observe this, when using offline maps everything works anyways, but when switching to online maps everything becomes really slow. Maybe the online maps are broken somehow. As far as I know @karry runs his own server for the map tiles, maybe the system is down somehow.

1 Like
5

Indeed, got the same. So, no idea here.

6

I get this every time when I launch it from the app drawer, but never when I launch it from the command line. I thought it picks something up on the command line, but it’s not as simple as that apparently.

7

It seems this will be fixed in next version :

4 Likes
8

We are allowed to have url handlers in the applications distributed via Harbour from the end of 2025 (see community news). But the launcher invokes the url handler (D-Bus method) on every startup, even there is no url to open. So, we need to filter out empty urls and do not show error. It will be fixed in next release.

4 Likes
9

Thank you for clarifying!

10

This time I need help- I just can’t get osm scout to work on the new J2. Installing had hiccups, repeatedly showing a “not found”; ultimately it seemed to be set up. But it just won’t open, only showing the running circle. Simple deinstallation didn’t help.

11

No idea how to help. Or perhaps trying in terminal?
But just to indicate that it works on the Jp2 here.

1 Like
12

The installation troubles lead me to believe something or other didn’t get installed properly. Could you open the Terminal app and run the following command?

devel-su

Tap enter, type in your developer mode password, tap enter again, and then run this:

version --dup

I have a feeling it’ll update or install some things.

1 Like
13

NO UPDATES FOUND.

But I tried something else- the nonfunctional download was v3.0 from openrepos/storeman. Deleted it, installed 2.43 from harbour- which then worked. Until I then updated it to 3.0, and once again, it’s broken.
Could there be something wrong with 3.0 specifically?

2 Likes
14

There is reported crash on J2 phone: Segfault on startup, v3.0.0 on Jolla Phone 2026 (Sailfish OS 5.2.0.17) · Issue #348 · Karry/osmscout-sailfish · GitHub

Any help is welcome, I am unable to reproduce it.

15

I tried the 3.0-1 without piper, but the result is the same. I only downloaded this one, should I install the two debugs as well?

16

It is crashing for me as well.

1032×2272 755 KB

17

Ok, so the next step is to use older sdk. I will provide testing packages tomorow (clean build takes several hours on my machine)

1 Like
18

Thank you! Not to forget that maybe it’s just another manifestation of the JP2 launcher defects, like gPodder feedback - #160 by bababasti and many more reports

19

For me it doesn’t start anymore as well on JP 2026 with version 5.2.17, but with the preceding version it did work

20

Thank you for the inputs. It is pretty strange…

You can also try builds from OBS:

older SDKs are not usable with Piper, as onnx runtime requiring newer CMake…