"HERE" displays "Couldn't show you this place now" errors

[Sebastien Bacher]

Using rtm 247
- click on the HERE icon
- look for a place (e.g type "burger" and tap one of the results)
- click on a "pin" on the map to get details

-> instead of having details on the location you selected it displays a "Couldn't show you this place now" error, details were displayed before (didn't try for some time so not sure when it started to return errors), using the here.com website from the browser doesn't expose that issue

[David Barth (dbarth)]

Can reproduce the issue on my krillin running r17 or 18 with the standard Here maps click.
There is nothing specific in the app logs when that happens.

It may be due to the geo-location information we send to the Here online service which may be wrong.

For reference Jibel indicates the problem appears on rtm only, whereas the same scenario works ok on vivid.

[David Barth (dbarth)]

Also note that the bug does not occur in the browser.

[Jean-Baptiste Lallement (jibel)]

On vivid/krillin, with HERE installed it works fine (I can call, see the nearest places and no error message)
oxide on vivid is 1.4.2-0ubuntu2
oxide on RTM is 1.4.2-0ubuntu0

[Dave Morley (davmor2)]

The fact that it is working in the browser as expected but not in the webapp makes me wonder if there was an api change between 1.3 and 1.4 and the web app framework is still using the 1.3 api calls.

[Olivier Tilloy (osomon)]

I can reliably reproduce the issue with the latest rtm-proposed image on krillin.

[Alexandre Abreu (abreu-alexandre)]

I could not repro it even after a clean reinstall of the latest stable image on krillin (and obviously not on -proposed). It must either be something transient or something specific to what being served by heremaps given your locations (plain website bug or something failling due to what's being sent)

[Sebastien Bacher (seb128)]

@Alexandre, it's not transient, it has been consistently hitting the bug for some time. It's also not likely a website bug, because using the website in the webbrowser on the same phone works correctly...