Messages

Fixed.

[Test environment:]

Damn, I can't reproduce it with rc1 version! Can you check if my steps are correct?

Test environment:

• Locus Pro ver. 2.20.2
• Geocaching4Locus ver. 1.5.4.3-rc1

Steps:

• Import any mystery cache which doesn't have filled-in changed coordinates (e.g. GC2Q9RP) to Locus - G4L -> Import GC, G4L set to download complete cache data
• Open cache in a web browser (GC2Q9RP) and press the pencil symbol which is placed after coordinates. Fill-in different coordinates and press Submit button. Then press Accept button to confirm it.
• Now open that imported cache in Locus, via external application button select Update cache in a menu.
• Cache should be now placed on a new coordinates.

Note: I tried it also with marked / unmarked "Move to final waypoint" and "Keep data while import", first two choices in Geocaching configuration section in Locus, but without any change.

Bad news - updating a cache with corrected coordinates is broken again (it was broken some time ago here).
To reproduce:
- download a mystery cache with corrected coordinates to Locus
- update the corrected coordinates to some different coordinates via GC website
- open the mystery cache in Locus and choose Update cache - it is updated but the coordinates are still old ones.

Try this version: https://www.dropbox.com/s/ts0ixz4dpeck91w/Geocaching4Locus-1.5.4.3-rc1.apk

@menion: It's bug in add-on. Above version works OK with a latest Locus.

Could you remove the spin control for the amount of geocaches and replace it with a edit box where we just could change the amount. I find myself scrolling from 200 to 10, or 50  and then back to 200...
Or maybe you could add an editable combobox where you remember the last 10 amounts. This is the most flexible and user friendly.

There is already editable field, just touch on number in a middle. Change a value and touch on finish button (on keyboard) to apply value. See attached picture bellow (sorry for czech enviroment:)).

[Changes for version 1.5.4.2:]

Hello geocachers,

New version 1.5.4.2 was published on Google Play (it will be available in a few hours)

Changes for version 1.5.4.2:
• Cache and log images are now handled in Locus
• Updated to latest Locus API
• Require Locus in version 2.20.1.8 or newer

See first page...

Hi Eddie,

As KaHeMu said, better is to download specified count of geocaches around a point. Then Locus have all geocache data (if you have set to download full geocache data in the add-on preferences) and don't need to be on-line, see more here: http://www.geocaching4locus.eu/manual/nearest-caches.

Could you try this version:

https://www.dropbox.com/s/0frs6ahxxcpe2vq/Geocaching4Locus-1.5.4-rc4.apk

When I tried to update 571 caches with this version, it did not get an error any more.

Damn! I didn't expected that someone reach the limit of calling 30 requests per minute (one request will update 10 caches), because Geocaching Live API server is known for slowness. But as I tested, it's not problem now to reach the limit when you update more than 300 caches. I will try to fix it in a next release.

Hello Arcao,
  small problem for you http://forum.locusmap.eu/index.php?topic=3648.msg26205#msg26205 ... It's probably needed to put a small "sleep()" between requests.

Uff. I didn't expect that someone reach the limit because it's 30 requests per minute and as you knows the Geocaching Live API server is slow. The update process separate the list of caches to 10 caches per request.

I will look on it.

Edit: Ha, I am able to reproduce it when I am updating more than 300 caches. So the Geocaching Live API server is faster than I expected. 

Edit: Fixed in 1.5.4-rc4 https://www.dropbox.com/s/0frs6ahxxcpe2vq/Geocaching4Locus-1.5.4-rc4.apk

[Changes for version 1.5.4:]

Hello geocachers,

New testing version 1.5.4-rc3 was released.

Changes for version 1.5.4:
• Improved Live map support
• Added notification when Live map is working
• Added configuration choice to show notification even if the Live map is disabled
• Permission to access external storage because of sending geocaches to Locus is not required any more, internal storage used instead (this fix a lot of errors received recently)
• Fixed wrong handling of plain text short/long geocache description
• Fixed App start crashes
• Other minor fixes

If you want to join to beta testing (you will receive test versions automatically from Google Play), join to Google+ Geocaching4Locus beta testing community and follow instruction there.

Also you can download testing APK directly from here: https://www.dropbox.com/s/gvh4shu7gfpviw6/Geocaching4Locus-1.5.4-rc3.apk

Arcao, can you please check out this post - why updating cache with corrected coordinates (more than once) does not work?

Sorry for late answer. Fixed in version 1.5.3.

Sorry for corrected coordinates. When I wrote the stuff around this, there wasn't field IsCorrectedCoordinate. I will try to fix it ASAP. Today I'm returning back from vacation, so maybe at evening.

Problem with Sign in was fixed.

Message from Groundspeak:

Thank you for the email.  We are aware of the issue and have identified the problem.  We will be coordinating a release in the next 2 hours.  Once this release has been deployed and we have confirmed the issue is fixed we will let you know.

Thank you for your patience.

I wrote e-mail to Groundspeak. I hope they fix it ASAP.