search

BaijnathG / mytracks

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

HG Repository Explorer shows old code #379

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1.Get TortouseHG for windows
2.clone the code into a local directory - it supposed to get the latest code;
3. Open TortouseHG Repository Explorer 

What is the expected output? What do you see instead?

Expected: the latest tagged version to be 1.1.2; contrary, it shows the latest 
update on Feb 4th, and the latest tagged version # 1.0.21 

After the build, it doesn't show the map; the released 1.1.2 works as expected, 
with the map. The build target is 2.3.1 Google API

What version of MyTracks are you using? On what version of Android? On what
phone? N/A to this issue

If possible please provide a log.  Either upload here or send to mytracks-
support@google.com.
Detailed instructions can be found here:
http://code.google.com/p/mytracks/wiki/HowToReportErrors

Please provide any additional information here:

Original issue reported on code.google.com by vlad.per...@gmail.com on 4 Mar 2011 at 3:46

GoogleCodeExporter commented 9 years ago 
I see two separate issues here:

1 - Something related to TortoiseHG, which I think you should report/ask the 
authors of that application about - unfortunately none of us has a Windows 
machine to try to test this on, so the best I can do is suggest that you bring 
up the change graph and try to update to the newest revision, which right now 
is f9d39e8b66. If you see the same behaviour with the command-line hg client, 
then please do let us know. (personally, I'm using hg 1.7.3 and MacHg 0.9.14, 
with which I see no similar issues)

2 - The map not showing is because the Maps API key that's set in the 
mytracks_layout.xml file corresponds to the key we use to sign the application 
for release. If you want the map to show up with a non-release build, you need 
to use your own API key, as described in detail here:

http://code.google.com/android/add-ons/google-apis/mapkey.html

(and if you're making changes, please remember not to commit the change to that 
API key)

Hope this helps.

Original comment by rdama...@google.com on 4 Mar 2011 at 5:14