rocketgarden

Interesting. Can you tell us what model phone you're using, and what version of android it's running? So long as you downloaded the app from the official Google Play store it should be fine; it's likely just a minor incompatibility with the icon included in the app that's causing it to use the default android app icon instead. Still, definitely something we'd want to fix, so thanks for bringing it to our attention!

For those of you whose devices are registering as having no compass, can I ask what the compass screen was displaying before? Would the compass face still rotate?

I suspect your only option may be to find a way to install Play Services. The Geocaching App relies on play services for map and location functionality, among other things. (Not sure how your google maps app is working without it - is it a modified version?) We've previously investigated third-party options that could replace google play services, but we don't have any plans to migrate to them at this time

The Samsung J6 lacks a hardware compass sensor. Unfortunately there's not much we can do on the software side, although we are working on improving the messaging so that users with no compass will at least have a better idea of why it doesn't work

You're missing the part where he said "despite the fact that mobile phones technically can't acquire better GPS accuracy". 10m is the most accuracy that a standard phone GPS can provide. Even if the sensor thinks it has a better reading, 10m (4 decimal places) is the margin of error The app itself doesn't actually do anything to cap the displayed number; the phone itself never reports a higher accuracy than 10m. Besides, if you get within 30 feet, it's time to start looking with your eyes!

If your OS is below 4.4, the app will stop working no matter what. You will need to update your device or acquire a new device with an OS version at or above 4.4 (or use the website) If you OS is between 4.4 and 5.1, the app might briefly stop working, but you can update to the latest Geocaching App version (via the play store) and it should work fine again If your OS is above 5.1, the system should handle the TLS switch and the app will keep working (although you should still update for the latest improvements & features!)

There's actually a second (secret? hidden?) gesture you can use to zoom the map with only one finger. Double tap, but hold down on the second tap and drag up/down to zoom. I use it all the time on google maps and it is very convenient compared to the pinch-zoom

To clarify, did you pay for premium in the app or on the website? Although either way, logging out and back in ought to fix it.

Disabled and archived caches are deliberately excluded from normal searches in the app. If you search for them by GC code or have them in a list then they can show up there.

We're aware of the issue and looking into a fix. Unfortunately, the magic of timezones means it's never an "easy" fix

If the compass isn't moving at all, it would suggest that your device doesn't actually have a compass, or that it's malfunctioning Do you know what the specific phone model is?

If you download a list for offline, the app will automatically download the OpenStreetMap tiles around the caches in that list. Currently that's the only way to download offline maps

Downloading lists for offline also downloads maps in the vicinity of caches in the list, which adds quite a bit of download time

We've just started a tiny rollout. That little uninstall/reinstall issue is why we haven't pushed it out to everyone yet

We're hard at work on it! We hit some snags regarding how the Android version handles waypoints compared to iOS, but we are at this very moment in the process of ironing them out

Using driving directions to navigate to solved coordinates (or other waypoints) should be possible in the next release!

I've just checked, and it looks like there is currently an ongoing Marketing Campaign to show a push notification to new users, which sounds like what you were seeing. It should only show up once; if it's more frequent that sounds like a bug on our part.

What cache were you seeing this on? The app should allow you to view all owner photos

In this case, it seems to be specific to airplane mode in particular. Being offline/out of service should work okay, although it's harder for us to test that case comprehensively. The problem is that in airplane mode, some phones "don't even bother trying" to make a network call, which causes the bug

We're currently looking into this bug, and we think we've tracked down the issue. A fix will hopefully be included in the 5.4 release (didn't make it in time for 5.3). What's happening is that when the app wants to load a geocache, it checks the database and the website/api. Normally the database is much faster than the network call to the api, so the cache loads fine. But in airplane mode, the phone is (occasionally) really proactive about cancelling the network call, so it fails instantly before the database check even finishes, and then the app thinks the whole thing failed to load. The only workaround right now is pretty much just not using airplane mode

Don't worry, attributes are coming in a future release

Sounds like you're referring to setting the default app for coord.info links? If you go to your phone's settings screen and find Geocaching in the Apps section, there should be a way to reset what it opens by default

You're right. Next time we bump our minimum version we'll try to be better about communicating this to users The google play store can take a while to update for all regions. I would suggest waiting a few more days for the updated version to show Not sure what you're referring to here. Our iOS and Android apps have been developed in tandem for the last 3 years, with feature releases usually happening within a few days of each other. We're not really favoring one over the other. And android may seem to have way more usage in certain regions, but overall it's pretty evenly split with iOS

The current version of the Geocaching App supports android OS versions 4.4 and above (KitKat/19 and up). Every so often (about 1-2 years) we increase the app's minimum supported version, when the number of people on older OS versions gets low enough, so that we can make use of features added by newer OS versions

Interesting, it should be showing the version number in the bottom left there. I'll look into that. You can also see the version number in the App Info screen, which can usually be reached on your phone via something like Settings->Apps->Geocaching