Unhelpful User-Agent for Android Garmin Connect Mobile

The User-Agent string for the Android version of Garmin Connect Mobile is
'Mozilla/5.0 ( compatible )'.

In contrast, the iOS version is 'ConnectMobile/12 CFNetwork/811.5.4
Darwin/16.6.0' which is *much* more helpful.

Given the recent JSON parsing bug in Android Garmin Connect Mobile, it's
really important to determine who is affected by the bug and provide them
information on fixing it (i.e. upgrading GCM). The current User-Agents allow
us to detect Android vs iOS but, since it doesn't provide version information,
we can't detect fixed vs unfixed versions of GCM.

Proposal

The Android version should use a User-Agent string modeled after the iOS
version with version information included.

Former Member over 8 years ago

Hey,

I've created a ticket to see what we can do.

Thanks,
-Coleman

rconradharris over 8 years ago

Looks like the same issue exists for the Windows Mobile phone version as well. It appears to be showing Apache-HttpClient as the user-agent. (Which honestly is a bit surprising, was thinking a more Microsoft-stackish library would be used, but that's looking too far behind the curtains...)

Former Member over 8 years ago

Hey,

The team discussed this and decided not to push for this change. As of GCM 3.20 the simulator, iOS, and Android should all behave the same way when it comes to types. You can ensure that code is compatible with the types GCM is returning by using instanceof checks. Thank you!

-Coleman