Pure Maps and HERE Maps - API key 2019 still good?

Applications
#1

Pure Maps 3.2.1-1.9.2.jolla (Chum) / Sailfish OS 4.5.0.18 / Sony Xperia III :

I installed Pure Maps after changing phone. All works OK, on-line (MapTiler at least) and off-line (OSM Scout Server). But when I tried the HERE online-profile it gets 401 http-errors when fetching tiles, i.e. it is not allowed to fetch them. I used the same HERE API-key I used in my previous phone 2019 - 2021.

I went back to my accounts in developers.here.com but everything seems to be OK (however, can’t remember having asked for a REST API key?). Has something changed with HERE API key since 2021? I am also confused between platform.here.com and developer.here.com, which one I should use now?

I am only interested in here.com’s traffic information, actually, not the maps, but it comes with them.

Traffic info in pure maps
#2

Yes, I had to switch to newer API keys system with HERE. That was in 2021.

To get new key:

4 Likes
#3

Thanks @rinigus - that was it. The trick for those who will be in the same unlikely situation, is that to get the “NEW” REST API key sticker visible, one needs to first suspend the old developer.here.com project, containing the old key, and then re-enable it (“Are you sure… Yes!”), et voilà !

An opportunity which I cannot miss to thank you thousand times for this amazing application!

2 Likes
#4

Hmm, afraid I got lost.
I registered as developper with a fictive app
Then I could Get a REST API but Pure Maps’s map stays gray although I entered the Access Key ID (or secret?) and restarted Pure Maps.
I didn’t see the ‘New’ sticker nor how to suspend the old account.

#5

zzzzzzz
zzzzzzz1922×1002 70.2 KB

In Pure Maps: you need to

Accept the HERE license conditions
Insert the API key (it is long… paste)

Then you would have a profile “HERE - online” available. If it still does not work, use journactl -f as devel-su on a terminal while you start the application. If you see http errors 401 you still have problems with you key (like I had above).

#6

Much thanks for having taken time.
Yes, I did those already.

The log talks about an error 403, not 401, but it’s still an autorization problem.

Mar 05 22:29:58 XperiaXA2-DualSIM [32189]: [W] unkn
own:0 - [ ERROR ] “{unknown}[Style]: Failed to loa
d tile 3/5/3=>3 for source raster: HTTP status code
403”
Mar 05 22:29:58 XperiaXA2-DualSIM [32189]: [W] unkn
own:0 - [ ERROR ] “{unknown}[Style]: Failed to loa
d tile 3/4/3=>3 for source raster: HTTP status code
403”
Mar 05 22:29:58 XperiaXA2-DualSIM [32189]: [W] unkn
own:0 - [ ERROR ] “{unknown}[Style]: Failed to loa
d tile 3/4/2=>3 for source raster: HTTP status code
403”
Mar 05 22:29:58 XperiaXA2-DualSIM [32189]: [W] unkn
own:0 - [ ERROR ] “{unknown}[Style]: Failed to loa
d tile 3/5/4=>3 for source raster: HTTP status code
403”
Mar 05 22:29:58 XperiaXA2-DualSIM [32189]: [W] unkn
own:0 - [ ERROR ] “{unknown}[Style]: Failed to loa
d tile 3/5/2=>3 for source raster: HTTP status code
403”
Mar 05 22:29:58 XperiaXA2-DualSIM [32189]: [W] unkn
own:0 - [ ERROR ] “{unknown}[Style]: Failed to loa
d tile 3/4/4=>3 for source raster: HTTP status code
403”
Mar 05 22:29:58 XperiaXA2-DualSIM [32189]: [W] unkn
own:0 - [ ERROR ] “{unknown}[Style]: Failed to loa
d tile 0/0/0=>0 for source raster: HTTP status code
403”
Mar 05 22:29:58 XperiaXA2-DualSIM [32189]: [W] unkn
own:0 - [ ERROR ] “{unknown}[Style]: Failed to loa
d tile 3/5/1=>3 for source raster: HTTP status code
403”
…

I’ll dig more and try again.

#7

If this is the first time you use the HERE developer’s account, you should see the NEW badge. I have an old account and an old project in it, in which I did not see (1) only (2). I had to go to the project (3) and cancel (4) it. Then I was able to restart it. After which the NEW badge appeared.

abbbbbbbbbbb
abbbbbbbbbbb1144×1933 173 KB

1 Like
#8

Thanks canne.
:man_facepalming: ~I just didn’t see I had to enable the access key under the OAuth tab. (No clear idea what this is, if it is related, but it is working now.)~
edit: I believe I did enable both API key and OAuth. But only one enabled API key is necessary. Nothing to do under the OAuth tab.

edit: actually, only HERE maps were working but not the HERE routing.
Now, both are working. Details here.

Sorry for the mess…

2 Likes