HEADLANDERS

I'm seeing exactly the same thing. It happens every time I launch the app. After several attempts, it finally connects and gives the search results and then behave until the app is restarted. This seems to coincide with the recent Web Site Maintenance and NOT the upgrade to the app. This needs attention. Will this thread get the attention of the Web site devs or should the issue be raised elsewhere?. Bill.

My main problem still with the 'Geocaching App' is when is frequently seems to loose it's GPS 'lock' or something like that when navigating and walking towards a cache location. Quite randomly the pulsating blue GPS 'dot' will stop moving as I walk. The app itself is not 'locked' though. Even restarting the Geocaching app does not make it regain it's GPS lock. It is not a problem with the phone or it's 'location services' because if I start up another Navigation App the GPS works fine. The only way to resolve this and reset it seems to be re=boot the phone. I know this has been mentioned on the iPhone App 'blog' but not sure what attention it is being given. I'm not sure either if it existed before the recent update. Bill.

Right, I understand the reason for this. It all makes sense now. I do have a more concerning issue regarding log date stamps and an inconsistency between viewing logs on the web site and viewing on the iPhone app. My personal belief is that the 'app' has the error. I will repeat this issue here for other who may not have seen the other posts as it is related: 'When a log is edited on the web site, the original 'logging' date stays the same which is quite important. However, using the iPhone app the 'log date' is always shown as the date that the log was actually last updated. This is confusing for both the finder and others. It puts thing out of chronological order. Please make these dates appear the same in the app as on the web site. ---my belief is that their is a bug in the iPhone App which is resulting in the wrong database field being selected for displaying the 'logged' date in the 'app'. The date being picked up by the 'app' display is in fact the date the last time the log was either created or even edited. This is not helpful at all as people viewing past logs want the date to represent that when the cache was actually found. I would hope for a change in the code in the 'App' so that it matches the log dates shown on the web site. Bill.

Yes, I reset them in both places several times to try to overcome this. I looked at a couple of your recent cache logs (PamplinMan's, too). They don't have time stamps. Can you be more specific about what the problem is? I can give you an example of exactly what I mean. Have a look at the logs to cache GC2HHWQ. You will see a Maintenance' log by ourselves dated November 20. We edited that log at 09.45h and I made a note of that within the edited text. However, when you look at the automated 'edit' dates/time added at the bottom of the log you will see that it is given as 01:48:15 which is exactly 8h earlier than the local time here. I repeat that my time-zone setting is correct in my 'Geocaching.com' profile 'Your Account Details' and after just re-checking it is selected as: 'GMT Greenwich Mean Time. Any help to understand this would be appreciated. Bill.

Yes, I reset them in both places several times to try to overcome this. I've tried this but it still doesn't change the behaviour I see. Bill.

I also had various problems when I update from version 4.1.3 to 4.2. I solved this by completely uninstalling Geocaching from the iPhone. Then updating the app in iTunes on my PC, then re-sync-ing the iPhone with iTunes so that the new version is installed on the iPhone. Obviously I lost any my settings and saved items but that was easily remedied. I had a feeling that doing it the 'update' way on the iPhone itself did not completely replace all the older version files with the newer ones. I hope this helps someone. Bill.

Even though I have set my date Time setting to 'Greenwich Mean Time (United Kingdom)' in my Profile Settings, when I post a log or edit a log it puts a timestamp on it which is 8 hours behind (Pacific USA time I guess). How can I overcome this?. Is there some other place I haven't found to change the settings?. Bill.