This object is in archive! 
Problem with logging of cache and LoMaps
Solved
Hello !
For two days, new update of Locus:The geocaching functions are displayed in errors (maps, logs)
Chrystelle
Hello !
For two days, new update of Locus:The geocaching functions are displayed in errors (maps, logs)
Chrystelle
Hi Chrystelle,
could you please provide us with more detailed information about the errors? Describe step-by-step how you come to an error, attach screenshots of the error or any error messages... Thanks!
Michal
Hi Chrystelle,
could you please provide us with more detailed information about the errors? Describe step-by-step how you come to an error, attach screenshots of the error or any error messages... Thanks!
Michal
Hi all,
thanks for additional information. Miloo974 wrote about two problems which are unfortunately in a single topic.
So the first problem with the map: it really does not look like "Hike & Bike" maps. It is also weird that on the main map screen is not visible bottom "Attribution".
Check please once more used map. It should look exactly like on my screenshot.
Problem with the login of caches is more interesting. is there possibility that you all have an unfinished upload of trackables log? Anyway, I've created a new version, so if anyone has a while, please test it if there will be the same problem.
How to:
install this special Beta version APK file (Beta version is just unlocked Free version as we describe here, so simply install it together with Pro version).
Start it, use it, try to do the action that causes a problems and we will see. If there still be any issue, in Locus/logs directory should be created a log with extra information. Share it with me please, thanks all!
Menion
Hi all,
thanks for additional information. Miloo974 wrote about two problems which are unfortunately in a single topic.
So the first problem with the map: it really does not look like "Hike & Bike" maps. It is also weird that on the main map screen is not visible bottom "Attribution".
Check please once more used map. It should look exactly like on my screenshot.
Problem with the login of caches is more interesting. is there possibility that you all have an unfinished upload of trackables log? Anyway, I've created a new version, so if anyone has a while, please test it if there will be the same problem.
How to:
install this special Beta version APK file (Beta version is just unlocked Free version as we describe here, so simply install it together with Pro version).
Start it, use it, try to do the action that causes a problems and we will see. If there still be any issue, in Locus/logs directory should be created a log with extra information. Share it with me please, thanks all!
Menion
Oh, sorry. I did not know that I had to create two subjects.
Thanks for the info, I'm doing it tomorrow. I tell you if it worked. Thank you
Oh, sorry. I did not know that I had to create two subjects.
Thanks for the info, I'm doing it tomorrow. I tell you if it worked. Thank you
Hehehe ;-) I have tried the linked Beta version (3.37.1.1) for the problem with the loging of caches. When i checked last three unloged caches in FieldNotes addon and selected the "Log selected", than the Locus Pro version was launched and caches are forwarded there. Then the message with czech string equal to "no applications are available" and then obviously the same error: kl, code: 10601.
Is there any way how to temporarily force the hook for loging is registered in the Beta version?
The logs are pure "Found it" on three traditional caches, no trackables.
I have some feeling that the error may be related to Opera which I have as a default browser.
Gimli2
of topic: I am not sure if it is better to write these reports in CZ or EN?
Hehehe ;-) I have tried the linked Beta version (3.37.1.1) for the problem with the loging of caches. When i checked last three unloged caches in FieldNotes addon and selected the "Log selected", than the Locus Pro version was launched and caches are forwarded there. Then the message with czech string equal to "no applications are available" and then obviously the same error: kl, code: 10601.
Is there any way how to temporarily force the hook for loging is registered in the Beta version?
The logs are pure "Found it" on three traditional caches, no trackables.
I have some feeling that the error may be related to Opera which I have as a default browser.
Gimli2
of topic: I am not sure if it is better to write these reports in CZ or EN?
@Miloo974
not a big problem, but better separate problems, because then more people may talk about a particular single problem.
@Gimli2
I prefer not to mix languages, thanks for understanding.
Ignore for now "Field notes" addon and log caches over Locus Map (Beta version) > menu > more > Geocaching Tools > Logs manager. Fact that "add-on Field notes" automatically opens Pro version seems to be small problem in this add-on. Thanks
@Miloo974
not a big problem, but better separate problems, because then more people may talk about a particular single problem.
@Gimli2
I prefer not to mix languages, thanks for understanding.
Ignore for now "Field notes" addon and log caches over Locus Map (Beta version) > menu > more > Geocaching Tools > Logs manager. Fact that "add-on Field notes" automatically opens Pro version seems to be small problem in this add-on. Thanks
At first: Thank you for pointing to internal logs manager. I had no idea that this feature was implemented.
The problem is unfortunately still the same. It ends with error: kl, code 10601. Before that, there was some flash message but was covered by modal panel/form/container (sorry, I dont know the android terms) with the name with actually processed cache and only the bottom edge of flash message was visible.
At first: Thank you for pointing to internal logs manager. I had no idea that this feature was implemented.
The problem is unfortunately still the same. It ends with error: kl, code 10601. Before that, there was some flash message but was covered by modal panel/form/container (sorry, I dont know the android terms) with the name with actually processed cache and only the bottom edge of flash message was visible.
Replies have been locked on this page!