Back again 
I guessed good:
[tankerkoenig] address= gps=false hideClosed=false radius=1 sort=price type=e5` apiKey=#my api key here#
solved the issue.
\o/
Back again 
I guessed good:
[tankerkoenig] address= gps=false hideClosed=false radius=1 sort=price type=e5` apiKey=#my api key here#
solved the issue.
\o/
I’ve made a ticket to remind me. It shouldn’t crash, in any case
I ‘thought’ it sent you to the settings page when the value was unset, but… I’ll see when I find the time.
Link to Ticket:

Announcing v0.2.4 - fixes for Prix Carburant Api changes. The apis were in better shape before, but at least we have reasonable performance again. Up on openrepos and github, coming to chum.
Still haven’t fixed the api selection page tankerkönig bug ![]()
Thanks a lot for this update !!!
Sure thing! It’s a bit sad since the api has been ‘simplified’ which means less information from Prix Carburant. But, it seems to work with some limitations. Please leave feedback or make a ticket on github!
For the moment i try the app just a little
Seems working fine. Except ccordinates seems not well formated for Pure Maps or OsmAnd+
Announcing v0.2.5 - geolocation backend fixes. Currently, Tankerkönig, Spritpreisrechner and Prix Carburants are functional but the Spanish backend seems to have changed completely. @carmenfdezb had you noticed? Up on openrepos, github and coming to chum …
That update completely broke the app for me.
After update, started it with ‘spritpreisrechner’ preset, shows ‘ungültige PLZ’, and then only leaves to swipe between (outdated) favourites and a blank page.
Restarting got me back to search page, so I tried to switch to ‘Tankerkönig’ just to experiment, since then the app gets stuck in ‘initialisiere’ and crashes completely.
Removing and reinstalling, same picture.
Update: deleting config got me back to step 1.
So, selecting Tankerkönig crashes the app without recovery (missing api key?). With Spritpreisrechner, i just can’t find any address or code that’s accepted for search.
Update2: ok, slowly getting beyond my own imbecility. Didn’t have any type of fuel selected (caution when switching between data providers). Now spritpreisrechner search by city name works, but postal codes are not accepted. Not able to search for more detailed location beyond name, so it’s decent in rural area, but search results for e.g. ‘Wien’ are a bit too unspecific.
It seems Spritradar doesn’t work for GeoportalGasolineras.es (Spain). I will take a look asap and I willtry to fix it. Thanks for notifying me!
Yes, I STILL haven’t fixed the no api key crash. Sorry!
And yes, postal code search is currently not possible. I had to switch geolocation back end and the only one that I could find on the quick only takes names, but globally. I should have mentioned in the announcement ! mea culpa, mea culpa …
Thank! I was hoping you’d say that. I’ll try to get the other bugs out ![]()
Oh, I forgot to ask… did you try a GPS search? That should get a more local/direct result …
I’m going to try to get location data caching (works well in an other context) and then it would work even with stale gps data.
Yes, GPS search did work.
So in next iteration I could copy geolocation coordinates from maps app into the search field?
Once again, thanks for your work!
Yes, there are a number of improvements to search in the works. I’m just bug triaging on too many fronts at once ![]()