SpiritGuide

The Wherigo player in Geooh GO for Android works just fine.

Geooh GO has a setting to use OS tile servers.

As I said, I have no idea what issues the other API apps are having. They may never have updated or could have similar implementation problems. I knew the GCDroid developer was having problems with Google and may have given up. CacheBox rarely has updates. The bottom line is no one but them know what's going on.

You totally misunderstood. Geooh also had OAuth 2.0 implemented YEARS ago since it first became available with the new API. The problem is if you had a minor parameter misspelling, there was no server error 500 all this time... the authentication server saw the error, didn't report it, and SILENTLY logged in using OAuth 1.0... so from outside appearances, how would you know that happened? Logins worked using your OAuth 2.0 implementation. How would you know that implementation was incorrect? How would you know your app wasn't ready? Only until the authentication server was prevented from falling back to OAuth 1.0 did the server 500 errors surface and digging around found the parameter problem. Everyone makes mistakes. Lucky you didn't mess up your implementation because the same thing would have happened to you. Thinking you had correctly set up the authentication, but not being notified it wasn't... because logins still worked. Groundspeak is responsible too since someone there designed the transparent fallback. From the very beginning the 500 error should have been thrown when an application sent invalid OAuth 2.0 login parameters. I managed developers and operations staff for too many years. If I had a server that was receiving errors, but no one looked at logs, or worse did look and said nothing... they'd be in my office for a come to Jesus meeting. You never let a server identify an error like that and just let it go like it was ok. And those errors were occurring for years! I have no idea if other API partner applications fell into this same trap thinking they did implement the correct OAuth 2.0 authentication only to finally discover this past week it was flawed. So until you know the full story stop pointing fingers!

Not completely true. Geooh GO was set up and doing the "required authorization method" years ago from the beginning of the API, but an incorrect parameter didn't surface until the new method went live. A technical mistake for sure, but one which Groundspeak could have prevented by reviewing server logs and informing partners of problems before go-live. I don't know about the other two apps, but don't assume application providers didn't try. Groundspeak can share some of the blame.

Which Android app? Maybe that's where the problem is.

Look at other apps that have built-in features like that.

It definitely is the app. On Android, developers decide how location updates are generated... the frequency from a previous update, and whether the device has moved a determined distance. To save on battery usage, the developer can dictate that the user has to move 100' for example before the OS gives a location update to the app.

Geooh GO does the same as Cachly plus more. Email support for assistance.

Did you try it with Geooh GO's Wherigo player? There's more than one Android app.

I've used multiple Pixel phones with the current model a Pixel 7 Pro. Everything will work just fine. Google even has tools to easily migrate from an iPhone to an Android so you shouldn't have any trouble there either.

But the Groundspeak checker is available in API apps so you don't have to go to the website.

Only if you have the Google Translate app installed.

Another reason to consider Geooh GO with its Android Auto app. It lets you see nearby geocaches on the car display while driving. Caches pop up on the HUD with an easy to see list on top of the map that moves/rotates with the car.

https://apidevelopers.geocaching.com/all-api-partners

Yes, Android operates the same. Select text, then a translate option is available without having to copy paste.

If you have the Google Translate app installed, the copy/paste pop-up will include a translate option... you don't need to copy it to the website.

Geooh GO can show all your logs (regardless of type) which includes photos. You can also search for specific ones based on type, dates, or GC.

WhereYouGo is not completely functional on newer Android versions. Although open source, it isn't being maintained or improved. WebWiGo is a web based player... it doesn't emulate any other players! The Geooh Wherigo player has an optional setting to display console output to the user which was designed to help cartridge developers. So I guess you could say Geooh is a player for players and an emulator for development when using GPS spoofing to help in bug fixing... according to your definition.

Or maybe I was providing a solution... he wasn't unclear to me, but maybe you are regarding Android apps on laptops.

Does running an Android app on a laptop including a GPS spoofing app from your couch count?

What is the difference between an emulator and a player?

The Wherigo player in Geooh GO auto saves for you.

Geooh GO for Android has optimized routing which can show three modes of travel and ETA.

Geooh GO includes a car app that runs on Android Auto on the car's display. It can show the nearest caches in an offline list on a map with a list on the side. See details of the cache then navigate to it without ever looking at your phone.