Cannot search

[Themightyimp]

Hi Guys and girls,

I am running tomtom go mobile 1.17 with UK map 990.8307 on a OnePlus5. It had worked fine previously. Recently I cannot search correctly. When I go into search (definitely not the recent destination search) and start entering a postcode (where it says "enter an address or name") day bs1 it says "no recent destinations start with bs1". Please help the shop is now useless.

Many thanks

 

[Arno]

Welcome to TomTomForums.

Can you elaborate a bit more on your search term as Google does not know what to do with it either.

 

[canderson]

I'm confused too, Arno. I could understand a "BS1 XXX" post code somewhere in the Bristol area, but one starting with "DAY"? They don't have post codes that start with three alpha characters.

However, I'm guessing that there's just a typo in there somewhere, and he really is attempting to enter a BS1 (Bristol) post code, and that his post code file from TT is missing or corrupt.

To the OP: Have you performed any updates of any sort since it was behaving correctly before?

 

[canderson]

To the OP:
I meant to ask, what is meant by "Please help the shop is now useless."? What shop?

 

[Themightyimp]

Welcome to TomTomForums.

Can you elaborate a bit more on your search term as Google does not know what to do with it either.

View attachment 4880

Apologies - Autocorrect issues.

I meant "say BS1" - to be clear I entered a postcode starting with BS1. If I enter anything like London or Bristol or a postcode (indeed any search term) I get the same answer "no recent destinations start with". Again to be clear it is not an incorrect postcode or place name. Even entering "BS" or "Bris" (I.e. The start of a postcode or a city name) gets the same result.

I've tried resetting the app, uninstalling and reinstalling with no joy.

 

[Themightyimp]

To the OP:
I meant to ask, what is meant by "Please help the shop is now useless."? What shop?

Again autocorrect issues.

I meant the app is now useless.

 

[Arno]

No idea what is wrong with yours as I get with 1.17 and 990.8307

 

[canderson]

There's a specific file involved for post codes, and that appears to be the problem. You're going to need to contact tech support to see if they can sort it. We've seen occasional map updates in the past where post code files were omitted or incomplete, causing the symptom you have. That may be the case here.