darodriguezalv / mytracks

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

Cannot save hikes any more since My Tracks was updated #1289

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1.My Tracks will not save my hikes any more.
The last hike I was able to save was on March 6. After that My Tracks was 
updated. Since the update I cannot save my hikes. I press the save and it 
disappears. What do I need to do to fix this?
2.
3.

What is the expected output? What do you see instead?
I expected to see the new hike on top and the rest of the hikes under it.
But it shows the last hike is Mar 6, than Feb 27, and so on. 
It neveer adds the new hike in.

What version of MyTracks are you using? On what version of Android? On what
phone?
My Track Version I think is 2.0.4
Samsung SCH-S720C
My phone Fiemware is 2.3.6
It worked before My tracks was updated.

If possible please provide a log by uploading here.
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 skipper1...@gmail.com on 16 Apr 2013 at 4:33

GoogleCodeExporter commented 9 years ago
Can you include your log? Start My Tracks, record a short track and stop.

Original comment by jshih@google.com on 18 Apr 2013 at 5:27

GoogleCodeExporter commented 9 years ago
Start My Tracks, record a short track and stop. I cannot figure how to log
it. The menu button does not give me anything. How do I log it? The only
thing I can do is press save.

Thanks for your help on this.

Tom

Original comment by skipper1...@gmail.com on 22 Apr 2013 at 6:40

GoogleCodeExporter commented 9 years ago
Can you see if the new track is on the bottom of the list?

There was a bug that caused some new tracks to appear on the bottom of the 
list. It has been fixed and will be in version 2.0.5.

Original comment by jshih@google.com on 11 Jun 2013 at 1:02

GoogleCodeExporter commented 9 years ago
I suspect it is due to issue 1282. Will be fixed in version 2.0.5.

Original comment by jshih@google.com on 17 Jun 2013 at 8:06