An issue I'd starred had some life again today.<br><a rel="nofollow" targ...

Julian Bond - 2014-05-22 06:59:12+0000 - Updated: 2014-05-22 06:59:12+0000

An issue I'd starred had some life again today.
https://code.google.com/p/google-plus-platform/issues/detail?id=620

Sadly, it's not good though. currentlocation in people.get never returns any data contrary to the documentation.
https://developers.google.com/+/api/latest/people

This was reported in July of last year prior to Latitude being closed down. It's been starred by 52 people.

Please Google, fix the bug in the API and/or fix the documentation. Or at the very least respond on the issue and explain what's going on.

This is a classic example of my occasional rants about the lack of developer engagement both here and on the issue tracker. Developers go to the trouble to find, investigate and report bugs and feature requests but it falls into a black hole.

See here for plenty more examples, More than 20 stars means it's probably important,
https://code.google.com/p/google-plus-platform/issues/list?sort=-stars

Conversely we get issues like https://code.google.com/p/google-plus-platform/issues/detail?id=735 that are still marked as open, despite apparently having been fixed.

google-plus-platform

Raymond Thornton - 2014-05-26 01:36:30+0000

Hey there i'll here u out my friend so what's up with your issue let it out free your mind (R T 1975)

Julian Bond - 2014-08-26 07:03:08+0000

Well this is bizarre.
https://code.google.com/p/google-plus-platform/issues/detail?id=620#c34

As of August 13, currentLocation is no longer listed as a valid field for the People API. https://developers.google.com/+/api/latest/people

Which perhaps explains why checkin and so on no longer change the "Lives in " to "Currently in " on your profile. It seems Google has simply dropped (more or less) real time location tracking.