Unable to geocode text entered Options

[2cats&amac]

I am very frustrated to have spent $10 for an app (which is extremely expensive to me) and I can't get it to work. I've searched the forum, found only one mention of a problem, with no solution. I have entered the address by hand, I have entered it from my contacts. I have tried full address, I have tried postal code. I have tried various addresses. Every time is "unable to geocode text entered". I am taking my kids out today, and wanted to avoid printing sheets of paper.

Using ipod touch version 2.0 with updated software.

[YeOleImposter]

I am very frustrated to have spent $10 for an app (which is extremely expensive to me) and I can't get it to work. I've searched the forum, found only one mention of a problem, with no solution. I have entered the address by hand, I have entered it from my contacts. I have tried full address, I have tried postal code. I have tried various addresses. Every time is "unable to geocode text entered". I am taking my kids out today, and wanted to avoid printing sheets of paper.

Using ipod touch version 2.0 with updated software.

Hmm, I had never tried the geocode feature before but I have to agree, the geocode feature is completely broken. Nothing I put can be processed, even a simple zip code. I am using an iPhone 3Gs with 3.01 -- so it is not a iTouch issue.

[2cats&amac]

Since we were out yesterday and the cache we looked for is gone, I was trying to find another one to do with the kids. I want to be able to quickly enter my current address and find nearby caches. It is the whole reason I purchased the app, and at this point I want my money back.

[Hrethgir]

Why don't you just use the "Find Nearby Caches" button? It will show you caches around where you currently are.

[2cats&amac]

Why don't you just use the "Find Nearby Caches" button? It will show you caches around where you currently are.

ipod touch does not have gps. It thinks I am in Seattle (I'm not)

I know I have seen another application that finds your location from the nearest wifi, but this one doesn't seem to.

[isuquinndog]

When you were using it at home you were connected to WiFi, right?

[isuquinndog]

I guess I don't understand the geocode question. The GC code or some thing else?

[spstanley]

The error comes up in the new 2.3 version of the application when you choose "Search by Address/Postal Code" and enter any search criteria, then choose Search. I've been having this problem with my iPhone 3G running OS version 3.0.1. It doesn't matter whether I enter the address or ZIP code by hand or choose from the contact list; all attempts result in the error response. And that's regardless of whether I'm using EDGE, 3G, or WiFi.

I first noticed the problem when a friend asked me to find caches near his brother's home in another state. Since I'm not there, I can't use "Find Nearby Caches" instead. ;-)

[2cats&amac]

When you were using it at home you were connected to WiFi, right?

Yes, I was at home on wifi. It is as described in the post by spstanley (a much clearer post than mine, thankyou). In the update for the app, it says the address thing was fixed because it used to only work with U.S. addresses. I can't get it to work with those either. I don't understand how this got past apple, I thought they really looked at these apps.

[isuquinndog]

I've never used that so I didn't know it was broken. But lookie at that, it is broken.

[ZSandmann]

It is broken on my 3GS running v2.3

[Echomalinois]

I have had no problems in putting a zip code on my phone till today. Perhaps it is having a problem talking to geocaching.com for some reason.

[Ash Scott]

I too am having this same problem. Entering any UK town returns the error but the same town entered at geocaching.com returns results.

I'd at least expect some acknowledgement from the developer that this is a problem being worked on.

It spoils an otherwise great app.

[2cats&amac]

I too am having this same problem. Entering any UK town returns the error but the same town entered at geocaching.com returns results.

I'd at least expect some acknowledgement from the developer that this is a problem being worked on.

It spoils an otherwise great app.

Response to my email summed up: "You're entering the address incorrectly".

Colour me not impressed.

[pjsanders]

So what is the "correct" way they suggested? I was surprised that just entering the zipcode didn't work

[Ash Scott]

So what is the "correct" way they suggested? I was surprised that just entering the zipcode didn't work

I tried:

London (which works on geocaching.com)
UK postcode (with and without spaces)
US Zipcode
Address from my contacts

All return the same result.

This needs to be fixed. The app is useless for planning without it. It's only good now for 'Caches near me'.

I may pursue getting my money back through Apple.

[2cats&amac]

So what is the "correct" way they suggested? I was surprised that just entering the zipcode didn't work

That is part of what impressed me so much with the email. She didn't ask how I had done it, and she didn't tell me how it should be done.

[2cats&amac]

So what is the "correct" way they suggested? I was surprised that just entering the zipcode didn't work

I tried:

London (which works on geocaching.com)
UK postcode (with and without spaces)
US Zipcode
Address from my contacts

All return the same result.

This needs to be fixed. The app is useless for planning without it. It's only good now for 'Caches near me'.

I may pursue getting my money back through Apple.

I was thinking I want my money back too, but it is convenient for having the description etc if I download it at home. I don't have to print all sorts of sheets.

I think it is terribly overpriced though, especially since it has such a major flaw. I'm a little surprised it got past apple.

[2cats&amac]

Latest rely to my email about this problem:

Hi,

I was able to talk to one of our developers on the mobile team. They said that this is currently a bug that our developers are working on and will be fixed with the next release.

Thank you for you patience and understanding while we work this out.

Best Regards,
Jessica

[realbinky]

Latest rely to my email about this problem:

Hi,

I was able to talk to one of our developers on the mobile team. They said that this is currently a bug that our developers are working on and will be fixed with the next release.

Thank you for you patience and understanding while we work this out.

Best Regards,
Jessica

It works if you use lat/long. :
N 71 5.123 W 13 031.123

Of course, if there is a button that says "address from contact list" a regular address should work, but this is a work-around to allow planning, checking, etc.

This post has been edited by realbinky: Sep 4 2009, 10:27 AM

[JoshLytle]

The geocoding service we've been using just turned their service off. That's why things are failing; it was relying on an external service for this feature. We're fixing the issue on our end and using a service that shouldn't fail as easily. Unfortunately we'll have to do an update to the store to get this feature out to the users. This will take some time, but in version 2.4 this will work.

[Desert_Rat]

Thanks for the update. Just got this app and in the first couple of minutes this problem shows up. Nice to see you are fixing it.

The geocoding service we've been using just turned their service off. That's why things are failing; it was relying on an external service for this feature. We're fixing the issue on our end and using a service that shouldn't fail as easily. Unfortunately we'll have to do an update to the store to get this feature out to the users. This will take some time, but in version 2.4 this will work.

[Beil]

I too just purchased this app yesterday and found this glitch right away. It's good to hear that it's going to be fixed (hopefully soon) as I am just getting into geocaching and it's a shame to have to start like this. (Yes, I know, this isn't the only way to GC but it's the only feasible one for me at the moment with a toddler in tow.)

Thanks for being on top of this App team. Makes me feel like my $10 was well spent knowing it motivates a quick solution.

[Skippermark]

The geocoding service we've been using just turned their service off. That's why things are failing; it was relying on an external service for this feature. We're fixing the issue on our end and using a service that shouldn't fail as easily. Unfortunately we'll have to do an update to the store to get this feature out to the users. This will take some time, but in version 2.4 this will work.

That probably explains why it doesn't work on the main site. When I enter my zip there it brings up some strange caches. Thanks Josh for letting us know.

[Dorsetgal & GeoDog]

The geocoding service we've been using just turned their service off. That's why things are failing; it was relying on an external service for this feature. We're fixing the issue on our end and using a service that shouldn't fail as easily. Unfortunately we'll have to do an update to the store to get this feature out to the users. This will take some time, but in version 2.4 this will work.

Josh, can you be any more specific on the timescale please?

[Fredact]

I too just purchased this app yesterday and found this glitch right away. It's good to hear that it's going to be fixed (hopefully soon) as I am just getting into geocaching and it's a shame to have to start like this. (Yes, I know, this isn't the only way to GC but it's the only feasible one for me at the moment with a toddler in tow.)

I also just purchased and was dissapointed. Glad to see it is fixed. A workaround in the meantime:

-"Find Nearby Caches"
-"View Results on Map"
-Zoom out (reverse pinch or use "-" button until you can see the area you really want to search)
-Move map to that area
-Zoom back in
-Press "Search here"

[JoshLytle]

The geocoding service we've been using just turned their service off. That's why things are failing; it was relying on an external service for this feature. We're fixing the issue on our end and using a service that shouldn't fail as easily. Unfortunately we'll have to do an update to the store to get this feature out to the users. This will take some time, but in version 2.4 this will work.

Josh, can you be any more specific on the timescale please?

I actually just submitted a quick fix update, version 2.3.1 just for this problem. It will now take as long as Apple takes. Probably a week or two.

[Dorsetgal & GeoDog]

The geocoding service we've been using just turned their service off. That's why things are failing; it was relying on an external service for this feature. We're fixing the issue on our end and using a service that shouldn't fail as easily. Unfortunately we'll have to do an update to the store to get this feature out to the users. This will take some time, but in version 2.4 this will work.

Josh, can you be any more specific on the timescale please?

I actually just submitted a quick fix update, version 2.3.1 just for this problem. It will now take as long as Apple takes. Probably a week or two.

Thanks for the update ... in both senses of the word - fingers crossed it comes through before I leave for a trip next week.

[Fredact]

In the meantime, as a work around, just use Find Nearby Caches, move the map to where you want to look, then do Search here.

[admo1972]

The updated app just got released, and solely addresses this issue. Haven't tried it yet, it's installing on my phone now...

Update: searching by zip, and bringing up an address from the address book also worked. Nice!

This post has been edited by admo1972: Sep 18 2009, 12:24 PM

[blb9556]

This issue only came up recently. Every box (zip, address etc) worked until recently. I'm sure this will be fixed soon. Have you entered home coords on the Geocaching website?

[JoshLytle]

This is now fixed. Version 2.3.1 is in the App Store.

[syte]

This is now fixed. Version 2.3.1 is in the App Store.

I have v2.3.1 and this is not fixed? what gives?

[JoshLytle]

This is now fixed. Version 2.3.1 is in the App Store.

I have v2.3.1 and this is not fixed? what gives?

What isn't fixed? Can you elaborate?

[Nip-N-Tuck]

I think he must mean it's still broke. I have 2.3.1 and still get Easter Island caches when searching a US zip code.

[backpacker144mhz]

I also get Easter Island caches when entering UK postcodes and place names.

[JoshLytle]

Well, we did fix an issue and a new one has appeared. We're working to fix it.

[gpleonard]

Well, we did fix an issue and a new one has appeared. We're working to fix it.

This was at the bottom of a response I received from Groundspeak today:

Ticket Details
===================
Ticket ID:
Department: Geocaching
Priority: Medium
Status: On Hold
Why is priorty medium and why is it on hold?

Thanks

[JoshLytle]

Well, we did fix an issue and a new one has appeared. We're working to fix it.

This was at the bottom of a response I received from Groundspeak today:

Ticket Details
===================
Ticket ID:
Department: Geocaching
Priority: Medium
Status: On Hold
Why is priorty medium and why is it on hold?

Thanks

There are a few things going on here. First, what you received was a response from our customer service team. I just talked with them and they explained that all new requests by default are assigned "Medium" priority and that they actually ignore that value and just handle things in the order in which they are received.

Second, the "on hold" status just means that the customer service team has processed the request and sent a response about it. Again, this is just their way of doing bookkeeping in the customer service computer system.

Third, the customer service team is separate from the mobile team. Bug fixes and new features go through me personally, and so I can promise that we're actually following through on this problem.