joelmap / geohashdroid

Automatically exported from code.google.com/p/geohashdroid
0 stars 0 forks source link

New Google Maps broke send to maps #47

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1.Select send to maps function
2.Choose Google MapsMaps
3.

What is the expected output?  What happened instead?

Expect to see hash point. Received location not found.

What version of Geohash Droid are you using?  On what phone?

0.7.17
Stock Verizon Galaxy Nexus

What version of Android is running on that phone, if you know?

4.2.2

Please provide any additional information below.

loc:##,## appears to work but snaps to nearest POI, parenthetical expression 
seems to be the issue.

Original issue reported on code.google.com by steve.ce...@gmail.com on 12 Jul 2013 at 2:13

Attachments:

GoogleCodeExporter commented 9 years ago
Hm, I see.  Yeah, looks like they broke the normal loc: format with this 
update.  Drat.

I'll get a workaround in sometime tonight, but like you said, it looks like 
it'll only snap to the nearest point of interest, which, when Geohashing, is 
rarely where you want to be.  Good thing I still have that warning in there 
when you send the point to the map.

Original comment by captains...@gmail.com on 12 Jul 2013 at 3:27

GoogleCodeExporter commented 9 years ago
Got it.  It'll now send a loc: without the extra label at the end, which should 
make it work again in the newer Google Maps versions.

This one I pushed straight to Google Play, and the new version includes the 
stock prefetcher, too.  Should be available for download soon, or just check 
the Downloads section here.  Thanks for the bug report!

Original comment by captains...@gmail.com on 13 Jul 2013 at 1:57

GoogleCodeExporter commented 9 years ago
It looks like Google Maps is working better without the loc: prefix. I got
an update for GMM today, version 7.0.2

Updates:
        Status: Fixed

Original comment by steve.ce...@gmail.com on 19 Jul 2013 at 5:28