Author Topic: Vers. 3.44.0 - problem to load pocket queries (geocaching)  (Read 363 times)

Offline Sibe

  • Newbie
  • *
  • Posts: 6
    • View Profile
  • Device: Samsung S9+ (Android 10), Samsung Galaxy Tab S3 (Android 9)
Vers. 3.44.0 - problem to load pocket queries (geocaching)
« on: February 20, 2020, 20:31:33 »
Since today's update it is no longer possible to download pocket queries from geocaching.com.
The message is displayed that you have to be a member (which I am) - ir$l,code 17000.

Please fix the error quickly, as a mega event is imminent and Locus is needed.
Many thanks in advance.
Best Regards
Sibe
 

Offline Viajero Perdido

  • Apprentice of Locus
  • **
  • Posts: 129
  • Thanked: 19 times
    • View Profile
  • Device: Samsung Galaxy Tab S2 (Android 7), Blackview BV6000s (Android 6), Nexus 7 (2013) for Alpha/Beta testing.
Re: Vers. 3.44.0 - problem to load pocket queries (geocaching)
« Reply #1 on: February 20, 2020, 22:52:11 »
It still works for me in 3.44.0, thank goodness.  This is mission-critical for me too at the moment.

Can you download the GPX files to your device manually, tap to open, and let Locus handle it?
 

Offline Sibe

  • Newbie
  • *
  • Posts: 6
    • View Profile
  • Device: Samsung S9+ (Android 10), Samsung Galaxy Tab S3 (Android 9)
Re: Vers. 3.44.0 - problem to load pocket queries (geocaching)
« Reply #2 on: February 21, 2020, 12:56:57 »
The manual download and implementation in Locus worked - luckily. However, this procedure should only be a temporary solution.
But thanks for the tip.

Best regards
Sibe
 

Online menion

  • Administrator
  • Professor of Locus
  • *****
  • Posts: 11651
  • Thanked: 367 times
    • View Profile
    • http://www.asamm.com
  • Device: SGS7
Re: Vers. 3.44.0 - problem to load pocket queries (geocaching)
« Reply #3 on: February 21, 2020, 15:40:26 »
Hi,
please just try to re-login, this may help. As I know, there should be no change in this behavior in the recent version.
Ideas, wishes, problems
Advanced topics, public discussion, sharing of knowledges, testing beta versions: you're here!
 

Offline Sibe

  • Newbie
  • *
  • Posts: 6
    • View Profile
  • Device: Samsung S9+ (Android 10), Samsung Galaxy Tab S3 (Android 9)
Re: Vers. 3.44.0 - problem to load pocket queries (geocaching)
« Reply #4 on: February 21, 2020, 16:18:25 »
Logging out and logging in did not bring a solution: I am only recognized as a basic member.

As a test, I also installed Geocaching4Locus => when I log on to Geocaching.com (worked without any problems), I am also only recognized as a basic member.

On Geocaching.com, however, nothing has changed in my membership status: I am still registered as a premium member.
The whole problem only came with the update to the current Locus version (shortly before I had used the app without any problems).
 

Offline Andrew Heard

  • Master of Locus
  • ****
  • Posts: 745
  • Thanked: 38 times
    • View Profile
  • Device: Samsung Galaxy A5 Oreo/8, Lenovo Note 4 Nougat/7.1
Re: Vers. 3.44.0 - problem to load pocket queries (geocaching)
« Reply #5 on: February 21, 2020, 22:15:32 »
apologies to others for cross  posting but @menion your new topic [APP] - version 3.44.+ ( 20. 2. 2020 ) does not allow a reply/ post from an ordinary user, or at least there is no REPLY button at bottom of page. Maybe just for me?
« Last Edit: February 21, 2020, 22:18:54 by Andrew Heard »
 
The following users thanked this post: menion

Offline Andrew Heard

  • Master of Locus
  • ****
  • Posts: 745
  • Thanked: 38 times
    • View Profile
  • Device: Samsung Galaxy A5 Oreo/8, Lenovo Note 4 Nougat/7.1
Re: Vers. 3.44.0 - problem to load pocket queries (geocaching)
« Reply #6 on: February 22, 2020, 21:46:00 »
fixed, thanks.
 

Offline Sibe

  • Newbie
  • *
  • Posts: 6
    • View Profile
  • Device: Samsung S9+ (Android 10), Samsung Galaxy Tab S3 (Android 9)
Re: Vers. 3.44.0 - problem to load pocket queries (geocaching)
« Reply #7 on: February 24, 2020, 23:27:24 »
The problem has solved itself since today - without any updates or a change in the settings.
So I suspect it was a problem with geocaching.com.
Thank you for your help.

Best regards
Sibe