This object is in archive! 

Inappropriate warning: Trackable must be held by user in order to visit a geocache

Paul Melching shared this problem 5 years ago
Solved

When I log a geocache I always get this warning (see attached screenshot):

  • Problem with the log of The Birtday Geocoin
    ("Message":"Trackable must be held by user in order to visit a geocache")
    KR, code: 403.

After clicking Cancel (Annuleren) the cache is properly logged (Found it).

I once possessed the Bithday Gecoin and selected the "Visited" checkbox when logging Geocaches. Since I dropped this geocoin (probably via geocaching.com) I get this warning message when logging a geocache.

Note that geocaching.com reports:

  • marianne&paul placed The Birthday Geocoin The Birthday Geocoin in Het geheim van het huis Junne

I get the same warning message when I click "LADEN" (Load Trackables) in the screen in which a geocache can be logged (see screenshot). The list of trackables stays properly empty.


How can I get rid of this inappropriate message?

Replies (5)

photo
1

Good day Paul,

it looks like you are stuck in situation, where Locus Map tries to send some pending trackable log, but this log is no longer valid.

To solve this, let's try to Open menu > Geocaching Tools > Logs manager. Here should at the top, visible option to send these logs, so give it a try. In case, logging of trackable failes, on error screen is an option "Discard log", which is what you need to press after fail. Thanks to this, you remove no longer valid log from Locus Map.

Let me know if this works, thanks.

photo
1

Hi Menion,

Thanks for your advice.

I used the Log Manager and it did contain a geocache log. It is empty now: It indicates No data ("Geen data"). However I still get the warning message when I click "LADEN" (Load Trackables) in the screen in which a geocache can be logged. I also restarted Locus. So I still have the issue.

Do you have other suggestions?

photo
1

Hello Paul,

little weird. Geocaching logs are stored in the file in your internal memory in Locus/data/config/gcFieldNotes.db . If you do not have any pending logs you need to send to gc.com and if you do not care about the history of logs in Locus Map, feel free to delete this file (or just rename for the test). It should solve your issue.

Menion

photo
1

Hi Menion,

Sorry for my late reply. After removing gcFieldNotes.db the issue is solved. Thanks for your support.

Paul

photo
1

Hello Paul,

perfect, glad to hear it. If it by any accident happen in the future again (hope no), send me please this database file. I'll try to simulate this issue and fix it permanently.

Menion

Replies have been locked on this page!