Android Cacher
update -> 2.3.15

small update …

- logs for geocaching should work again

lets see what will not work anymore after the update :)
…
My tests all worked, so please report problems!!!!

lets see what will not work anymore after the update :)

My tests all worked, so please report problems!!!!

update -> 2.3.14

fixed geocaching.com support (again).

enhanced my tests to be able to react faster to such stuff.

update -> 2.3.13

- fix for the new geocaching website … 

next time I will try to use some of the json response that the beta maps uses .. if the beta map still exists!!!

update -> 2.3.11

Another fixing round for geocaching.com. They changed the layout again, which broke the webcrawler badly. Additional to this they also changed the results in the nearest search in such a way, that a lot of useful information cannot be parsed anymore.

Please give it a try again.

update -> 2.3.10

bugfix for greg

- cacheowner implemented for opencaching sites

update -> 2.3.9

After quite a while there was a new comment in the developer console for the cacher.

Someone named Greg (no chance for me to get in contact with him) wanted support for different opencaching-domains.

Here you are :)

wonderful …

this tuesday, geocaching.com had an announcment about some work on their server.

i already feared, that this would lead to problems with the cacher, but today everything is still working … that was luck :)

update -> 2.3.8

After updating to the new sdk (2.3) I had to fix some problems in the strings.xml-files.

Then I tried the application and my new housecache included some stages with roman numbers. So the solver now can also handle this (just enter something like MCMLXXIV).

News and Noteworthy:

  • some fixes regarding progress dialogs and orientation changes while importing.
  • roman numbers in the solver.
  • special christmas offer … only 1.5€ instead of 3€!!!
  • a highres image for the new market (actually its the splash screen)
update -> 2.3.7

just got a bug report, that the radar intent for waypoints always navigates to somewhere in afrika (i suppose gps-position: 0,0). problem was that i fed doubles instead of floats into the radar intent.

give the new version a try!